Triple
T13381962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Education City Stadium |
E319338
|
entity |
| Predicate | plannedLegacyUse |
P12134
|
FINISHED |
| Object | university sports events |
—
|
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: university sports events | Statement: [Education City Stadium, plannedLegacyUse, university sports events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedLegacyUse Context triple: [Education City Stadium, plannedLegacyUse, university sports events]
-
A.
plannedUseOf
chosen
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
B.
legacyPlanning
Indicates the process of arranging how assets, responsibilities, and wishes will be managed and transferred to others in the future, typically after one’s death.
-
C.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
D.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
E.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce694788190881d1feac5b75720 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.