Triple
T9760289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monster Park |
E236650
|
entity |
| Predicate | namingRightsPeriodStart |
P15851
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Monster Park, namingRightsPeriodStart, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingRightsPeriodStart Context triple: [Monster Park, namingRightsPeriodStart, 2004]
-
A.
namingRightsEndYear
Indicates the calendar year in which an entity’s contractual right to have its name associated with another entity (e.g., a venue, event, or asset) expires.
-
B.
namingRightsChangeYear
Indicates the year in which the naming rights for something (such as a venue, event, or asset) were changed from one name or sponsor to another.
-
C.
acquiredNamingRightsYear
chosen
Indicates the year in which an entity obtained the naming rights to another entity (such as a venue, event, or organization).
-
D.
namingRightsLocation
Indicates that an entity holds the naming rights specifically for a given location or venue.
-
E.
namingRightsReplaced
Indicates that one entity’s naming rights to something have been superseded or taken over by another entity’s naming rights.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda049995c81908569ec61805642b2 |
completed | April 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.