Triple
T2183291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busch Stadium |
E49093
|
entity |
| Predicate | homePlateOrientation |
P37713
|
FINISHED |
| Object | roughly northeast |
—
|
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: roughly northeast | Statement: [Busch Stadium, homePlateOrientation, roughly northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homePlateOrientation Context triple: [Busch Stadium, homePlateOrientation, roughly northeast]
-
A.
gateOrientation
Indicates the directional alignment or facing direction of a gate relative to a reference frame or coordinate system.
-
B.
plateLocation
Indicates the spatial position or placement of a plate relative to a reference location or object.
-
C.
legOrientation
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
-
D.
servesDirection
Indicates that one entity provides service or functionality oriented toward, or in the direction of, another entity.
-
E.
shaftOrientation
Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc4358fc88190a6f556c2de9fef8c |
completed | March 7, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69abbda0ec948190be88c1243d81a423 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abc434978c8190b9c4dd8411b87f23 |
completed | March 7, 2026, 6:22 a.m. |
Created at: March 4, 2026, 7:45 p.m.