Triple
T11856732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilanowska metro station |
E282058
|
entity |
| Predicate | partOfLine |
P6309
|
FINISHED |
| Object | M1 |
E629456
|
NE 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: M1 | Statement: [Wilanowska metro station, partOfLine, M1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M1 Context triple: [Wilanowska metro station, partOfLine, M1]
-
A.
M1
M1 is Budapest’s historic Millennium Underground line, one of the world’s oldest metro lines and a UNESCO World Heritage site.
-
B.
M1
chosen
M1 is one of the main lines of the Bucharest Metro, forming part of the city’s core rapid transit network.
-
C.
M1
M1 is the region of the brain’s frontal lobe responsible for executing voluntary movements by sending motor commands to the muscles.
-
D.
M1
M1 is a central Manchester, England postcode district that covers much of the city centre’s commercial and cultural core.
-
E.
M1
M1 is a major north–south urban freeway in Johannesburg, South Africa, connecting the city center with key suburbs and routes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a699089c8190b7a298baf13dcded |
completed | April 10, 2026, 7:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f167d9b9e8819093582637941fc5ca |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 8, 2026, 9:43 p.m.