Triple
T31801422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fluor Field at the West End |
E811748
|
entity |
| Predicate | hasOutfieldWallHeightVariation |
P176045
|
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: [Fluor Field at the West End, hasOutfieldWallHeightVariation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutfieldWallHeightVariation Context triple: [Fluor Field at the West End, hasOutfieldWallHeightVariation, yes]
-
A.
outfieldWallHeight
Indicates the height of the wall that defines the boundary of the outfield area in a ballpark or playing field.
-
B.
outfieldWallType
Indicates the specific kind or configuration of the wall that defines the outer boundary of an outfield area.
-
C.
hasOuterWallWidthApprox
Indicates that an entity has an outer wall whose width is approximately a specified value.
-
D.
hasOuterWallLengthApprox
Indicates that an entity has an outer wall whose length is approximately a specified value.
-
E.
hasOuterWall
Indicates that one entity possesses or is surrounded by an external enclosing wall that defines its outer boundary.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: April 30, 2026, 11:41 p.m.