Triple
T3919961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hangar (Lancaster Municipal Stadium) |
E88933
|
entity |
| Predicate | hasOutfieldWallFeature |
P16726
|
FINISHED |
| Object | airplane statue |
—
|
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: airplane statue | Statement: [The Hangar (Lancaster Municipal Stadium), hasOutfieldWallFeature, airplane statue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutfieldWallFeature Context triple: [The Hangar (Lancaster Municipal Stadium), hasOutfieldWallFeature, airplane statue]
-
A.
hasOuterWall
Indicates that one entity possesses or is surrounded by an external enclosing wall that defines its outer boundary.
-
B.
outfieldWallHeight
Indicates the height of the wall that defines the boundary of the outfield area in a ballpark or playing field.
-
C.
hasOutfieldWallCovering
Indicates that an outfield wall is covered or surfaced with a particular material or type of covering.
-
D.
hasOutfieldFeature
chosen
Indicates that an entity possesses or includes a specific feature or characteristic located in its outfield area.
-
E.
outfieldWallDistance
Indicates the measured distance from home plate to the outfield wall at a particular point or area on the field.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.