Triple
T34099144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio Stadium |
E874515
|
entity |
| Predicate | previousFieldName |
P30138
|
FINISHED |
| Object | Tressel Field |
—
|
NE NERFINISHED |
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: Tressel Field | Statement: [Ohio Stadium, previousFieldName, Tressel Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousFieldName Context triple: [Ohio Stadium, previousFieldName, Tressel Field]
-
A.
formerField
chosen
Indicates that an entity previously had a particular field, role, or area of activity, but no longer does.
-
B.
updatesFieldName
Indicates that one entity changes or modifies the name of a specific field associated with another entity.
-
C.
previousStateName
Indicates the name of the state that immediately preceded the current state in a process or state transition.
-
D.
namedAfterField
Indicates that one entity has been given a name derived from or in honor of another entity, typically a person, place, or thing.
-
E.
previousEventName
Indicates that the value specifies the name of an event that occurred immediately before another event in a 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 1, 2026, 1:53 a.m.