Triple
T355352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foxboro Stadium |
E7529
|
entity |
| Predicate | fieldOrientation |
P1101
|
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: [Foxboro Stadium, fieldOrientation, north–south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOrientation Context triple: [Foxboro Stadium, fieldOrientation, north–south]
-
A.
orientation
chosen
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
B.
forceDirection
Indicates the direction in which a force is applied or exerted in the relationship between entities.
-
C.
sessionOrientation
Indicates the directional or spatial alignment relationship established between entities within a session or interaction context.
-
D.
hasRunwayOrientation
Indicates that a runway is aligned or oriented in a specific directional heading.
-
E.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebad8bf08190b4a38ffd9157d641 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e9589e7c8190b2d3af8f858c96af |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.