Triple
T1974650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodger Stadium |
E42880
|
entity |
| Predicate | outfieldFence |
P22064
|
FINISHED |
| Object | symmetrical dimensions |
—
|
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: symmetrical dimensions | Statement: [Dodger Stadium, outfieldFence, symmetrical dimensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outfieldFence Context triple: [Dodger Stadium, outfieldFence, symmetrical dimensions]
-
A.
outfieldWallHeight
Indicates the height of the wall that defines the boundary of the outfield area in a ballpark or playing field.
-
B.
outfieldWallDistance
chosen
Indicates the measured distance from home plate to the outfield wall at a particular point or area on the field.
-
C.
fieldSide
Indicates the relative side or position of something with respect to a defined field or playing area.
-
D.
fielded
Indicates that an entity deployed, presented, or put forward another entity (such as a person, team, or resource) for participation or use in a particular context or activity.
-
E.
homeBaseballField
Indicates that one entity serves as the primary or designated baseball field used as the home venue by the other entity.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f6c4208190a41e02733faed8df |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff9a09c8190a81fa13f4b85bc79 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.