Triple
T9477100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koopa Troopa |
E228541
|
entity |
| Predicate | recurringGameElement |
P52035
|
FINISHED |
| Object | platforming obstacle |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: platforming obstacle | Statement: [Koopa Troopa, recurringGameElement, platforming obstacle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recurringGameElement Context triple: [Koopa Troopa, recurringGameElement, platforming obstacle]
-
A.
gameElement
chosen
Indicates that one entity functions as a component, feature, or part within the structure or mechanics of a game.
-
B.
recurringEvent
Indicates that an event occurs repeatedly over time according to some regular pattern or schedule.
-
C.
recurringDuring
Indicates that an event or state happens repeatedly within the time span or context defined by another event or interval.
-
D.
featuresRecurringElement
Indicates that something includes an element, motif, or component that appears repeatedly over time or across multiple instances.
-
E.
hasRecurringProtagonists
Indicates that the same main character or set of main characters appears repeatedly across multiple works or installments in a series.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd801386948190890133f622ff360b |
completed | April 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.