Triple
T11428938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Steel Yard |
E270826
|
entity |
| Predicate | hasOutfieldWall |
P44339
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [U.S. Steel Yard, hasOutfieldWall, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutfieldWall Context triple: [U.S. Steel Yard, hasOutfieldWall, yes]
-
A.
outfieldWallHeight
Indicates the height of the wall that defines the boundary of the outfield area in a ballpark or playing field.
-
B.
hasOuterWall
chosen
Indicates that one entity possesses or is surrounded by an external enclosing wall that defines its outer boundary.
-
C.
outfieldWallDistance
Indicates the measured distance from home plate to the outfield wall at a particular point or area on the field.
-
D.
hasOutfieldWallCovering
Indicates that an outfield wall is covered or surfaced with a particular material or type of covering.
-
E.
hasOutfieldFeature
Indicates that an entity possesses or includes a specific feature or characteristic located in its outfield area.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c1bfb881909720c74fe0fa837f |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.