Triple
T25543280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central |
E640227
|
entity |
| Predicate | mapLabelFor |
P13793
|
FINISHED |
| Object | Central line |
—
|
NE NERFINISHED |
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: Central line | Statement: [Central, mapLabelFor, Central line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapLabelFor Context triple: [Central, mapLabelFor, Central line]
-
A.
mapLabel
chosen
Indicates that a label or name is assigned to a map or mapped entity for identification or display.
-
B.
mapCaption
Indicates that the value is a textual caption or label describing the associated map.
-
C.
mapsFrom
Indicates that one entity is derived, transformed, or constructed based on data, structure, or content originating from another entity.
-
D.
mapsAs
Indicates that one entity serves as a mapping or correspondence to another, typically translating or associating elements from one domain or representation to another.
-
E.
mapSymbol
Indicates a correspondence where one symbol is used to represent, stand for, or denote another element within a mapping or representation system.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f895e458819081cf031b70d20e56 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:27 p.m.