Triple
T4432960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notre Dame Stadium |
E95376
|
entity |
| Predicate | endZoneOrientation |
P55975
|
FINISHED |
| Object | north–south |
—
|
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: north–south | Statement: [Notre Dame Stadium, endZoneOrientation, north–south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endZoneOrientation Context triple: [Notre Dame Stadium, endZoneOrientation, north–south]
-
A.
hasRegionalOrientation
Indicates that an entity is oriented toward, focused on, or primarily associated with a specific geographic region.
-
B.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
C.
exportOrientation
Indicates that an entity’s activities, production, or strategy are primarily directed toward serving foreign or international markets rather than domestic ones.
-
D.
shaftOrientation
Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or object.
-
E.
legOrientation
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
- F. None of above. chosen
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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3556cd83881908547aa311c4f17fa |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:31 p.m.