Triple
T6668025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A10 ring road (eastern section) |
E151654
|
entity |
| Predicate | positionOnRing |
P64844
|
FINISHED |
| Object | eastern section |
—
|
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: eastern section | Statement: [A10 ring road (eastern section), positionOnRing, eastern section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnRing Context triple: [A10 ring road (eastern section), positionOnRing, eastern section]
-
A.
positionInRingSystem
Indicates the specific location or ordering of an object within a ring system relative to the system’s central body and/or other ring components.
-
B.
positionOnCityCircle
chosen
Indicates that one entity is located along the circular boundary or ring-shaped layout defined by a city.
-
C.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
D.
ringLocation
Indicates the spatial position or placement of a ring relative to a reference object or context.
-
E.
positionInRosary
Indicates the specific sequential place an element occupies within the ordered structure of a rosary.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.