Triple
T895129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oriole Park at Camden Yards |
E19326
|
entity |
| Predicate | hasOutfieldWallType |
P16726
|
FINISHED |
| Object | asymmetrical outfield 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: asymmetrical outfield dimensions | Statement: [Oriole Park at Camden Yards, hasOutfieldWallType, asymmetrical outfield dimensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutfieldWallType Context triple: [Oriole Park at Camden Yards, hasOutfieldWallType, asymmetrical outfield dimensions]
-
A.
hasOutfieldWallCovering
Indicates that an outfield wall is covered or surfaced with a particular material or type of covering.
-
B.
hasOutfieldFeature
chosen
Indicates that an entity possesses or includes a specific feature or characteristic located in its outfield area.
-
C.
hasBorderWallOrFence
Indicates that a physical barrier such as a wall or fence exists along the border between two entities.
-
D.
hasHullType
Indicates that an entity possesses or is characterized by a specific type or form of hull.
-
E.
hasBoundaryType
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad22b6fc819093e655c8ce1f738b |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa94f7c881908deeb62308942e19 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.