Triple
T37666267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jump Up, Super Star! |
E937825
|
entity |
| Predicate | featuredInLevel |
P626
|
FINISHED |
| Object | New Donk City Festival |
E2236999
|
NE 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: New Donk City Festival | Statement: [Jump Up, Super Star!, featuredInLevel, New Donk City Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredInLevel Context triple: [Jump Up, Super Star!, featuredInLevel, New Donk City Festival]
-
A.
featuredIn
chosen
Indicates that one entity appears or is prominently included within another entity, such as a person, work, or item being showcased in a larger work, event, or context.
-
B.
featuredInForm
Indicates that something is prominently included or highlighted within a particular form or form layout.
-
C.
playedAtLevel
Indicates that an entity participated or performed in an activity, event, or game at a specified level of difficulty, competition, or hierarchy.
-
D.
level1Feature
Indicates that one entity possesses or is associated with a primary or first-tier feature of another entity.
-
E.
locatedOnLevel
Indicates that one entity is situated on a specific floor or level within a multi-level structure or system.
- F. None of above.
Provenance (4 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40d66bcb9c8190a7c0643a8a24cccc |
completed | June 28, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.