Triple
T17427370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charleroi Metro |
E423773
|
entity |
| Predicate | hasLine |
P35
|
FINISHED |
| Object |
Line M1
Line M1 is a light metro route within the Charleroi Metro system in Belgium, serving as one of its primary urban transit lines.
|
E1268090
|
NE FINISHED |
How this triple was built (4 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 M1 | Statement: [Charleroi Metro, hasLine, Line M1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Line M1 Context triple: [Charleroi Metro, hasLine, Line M1]
-
A.
Line M1
Line M1 is a primary metro line of the Warsaw Metro system, running north–south through the city and serving key residential and commercial districts.
-
B.
Line M
Line M is a cable car line within the Medellín Metro system that serves hillside neighborhoods by connecting them to the city’s main mass transit network.
-
C.
Line L
Line L is a cable car line of the Medellín Metro system that serves hillside neighborhoods by connecting them to the main urban transit network.
-
D.
M41 line
The M41 line is a planned or operational rapid transit route within the Istanbul Metro system, serving as part of the city's expanding urban rail network.
-
E.
M19 line
The M19 line is a rapid transit route within the Istanbul Metro system serving commuters in Turkey’s largest city.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Line M1 Triple: [Charleroi Metro, hasLine, Line M1]
Generated description
Line M1 is a light metro route within the Charleroi Metro system in Belgium, serving as one of its primary urban transit lines.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Line M1 Target entity description: Line M1 is a light metro route within the Charleroi Metro system in Belgium, serving as one of its primary urban transit lines.
-
A.
Line M1
Line M1 is a primary metro line of the Warsaw Metro system, running north–south through the city and serving key residential and commercial districts.
-
B.
Line M
Line M is a cable car line within the Medellín Metro system that serves hillside neighborhoods by connecting them to the city’s main mass transit network.
-
C.
Line L
Line L is a cable car line of the Medellín Metro system that serves hillside neighborhoods by connecting them to the main urban transit network.
-
D.
M41 line
The M41 line is a planned or operational rapid transit route within the Istanbul Metro system, serving as part of the city's expanding urban rail network.
-
E.
M19 line
The M19 line is a rapid transit route within the Istanbul Metro system serving commuters in Turkey’s largest city.
- F. None of above. chosen
Provenance (5 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e448fdc1348190985db52c8c74c394 |
completed | April 19, 2026, 3:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01a80848fc8190b70d3612001cb9c7 |
completed | May 11, 2026, 9:57 a.m. |
| NEDg | Description generation | batch_6a01aa1065d081909a6f486a9000b191 |
completed | May 11, 2026, 10:06 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a01aa905d7c819090b27b0867c4c25d |
completed | May 11, 2026, 10:08 a.m. |
Created at: April 10, 2026, 5:46 a.m.