Triple
T5387693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington–Grizzly Stadium |
E120241
|
entity |
| Predicate | hasEndZone |
P6793
|
FINISHED |
| Object | student section |
—
|
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: student section | Statement: [Washington–Grizzly Stadium, hasEndZone, student section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndZone Context triple: [Washington–Grizzly Stadium, hasEndZone, student section]
-
A.
interceptionYardLine
Indicates the yard line on the field where an interception occurs during a play.
-
B.
hasZone
chosen
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
C.
decisiveTouchdownScorer
Indicates the player who scored the touchdown that ultimately determined the outcome of the game.
-
D.
hasHomeTeamSideline
Indicates that a particular sideline is designated as belonging to or used by the home team in a sporting event or venue.
-
E.
hasFreeZone
Indicates that an entity includes or is associated with a designated free zone area where special rules, privileges, or exemptions apply.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd86f8d81081909174027a4fe640f2 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.