Triple
T21847656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charpennes – Charles Hernu |
E539416
|
entity |
| Predicate | connectsMetroLines |
P18378
|
FINISHED |
| Object | Line A |
—
|
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: Line A | Statement: [Charpennes – Charles Hernu, connectsMetroLines, Line A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsMetroLines Context triple: [Charpennes – Charles Hernu, connectsMetroLines, Line A]
-
A.
subwayLine
chosen
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
B.
connectsMetroAreas
Indicates a relationship where a transportation route or service links two or more metropolitan areas, enabling direct travel or interaction between them.
-
C.
monorailLines
Indicates that there is a monorail transit line or system associated with, serving, or present in the referenced entity.
-
D.
metroLineColor
Indicates the color assigned to a specific metro or subway line in a transit system.
-
E.
metroLineInaugurated
Indicates that a metro line was officially opened and began operation on a specific date or during a specific event.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd558ed88190a10b8d6752105cd6 |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.