Triple
T22201173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobby Dodd Stadium |
E548686
|
entity |
| Predicate | hasPlayingSurfaceOrientation |
P12663
|
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: [Bobby Dodd Stadium, hasPlayingSurfaceOrientation, north–south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayingSurfaceOrientation Context triple: [Bobby Dodd Stadium, hasPlayingSurfaceOrientation, north–south]
-
A.
hasPlaySurfaceDimensions
Indicates the specific measurements or size characteristics that define the dimensions of a play surface.
-
B.
hasOrientationInUse
Indicates that an entity, when in use or operation, is oriented in a specific direction or spatial alignment.
-
C.
hasOrientation
chosen
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
D.
performanceOrientation
Indicates a relationship where an entity is characterized by a focus on achieving high performance, results, or measurable outcomes in its activities or behavior.
-
E.
sessionOrientation
Indicates the directional or spatial alignment relationship established between entities within a session or interaction context.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aeb16348190a34f96b47e01c8cf |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.