Triple
T5050175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meiji Jingu Stadium |
E113764
|
entity |
| Predicate | hasOutfieldConfiguration |
P13644
|
FINISHED |
| Object | symmetrical outfield |
—
|
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 outfield | Statement: [Meiji Jingu Stadium, hasOutfieldConfiguration, symmetrical outfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutfieldConfiguration Context triple: [Meiji Jingu Stadium, hasOutfieldConfiguration, symmetrical outfield]
-
A.
hasOutfieldFeature
Indicates that an entity possesses or includes a specific feature or characteristic located in its outfield area.
-
B.
hasInfield
Indicates that an entity possesses or includes a designated infield area, typically within a larger spatial or structural context.
-
C.
hasInfieldOval
Indicates that one entity possesses or includes an oval-shaped infield area as part of its structure or layout.
-
D.
hasConfiguration
chosen
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
E.
hasControlFields
Indicates that one entity possesses or defines control-related parameters, settings, or fields that govern the behavior or configuration of another entity or process.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7425df74819091cfde348dd16a68 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.