Triple
T10930762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurskaya |
E258198
|
entity |
| Predicate | line |
P1293
|
FINISHED |
| Object | Circle Line |
E59707
|
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: Circle Line | Statement: [Kurskaya, line, Circle Line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Circle Line Context triple: [Kurskaya, line, Circle Line]
-
A.
Circle Line
Circle Line is a mass rapid transit line in Singapore that forms a loop connecting key residential, commercial, and educational districts around the city.
-
B.
Circle line
chosen
The Circle line is a central London Underground route forming a loop through key districts and interchanges in the city’s transport network.
-
C.
Circular line
The Circular line is a driverless rapid transit line in the Taipei Metro system that forms a loop connecting multiple districts around the city.
-
D.
Circular line
Circular line is the nickname for Line 6 of the Madrid Metro, a heavily used underground route that forms a loop around central Madrid.
-
E.
Loop Line
Loop Line is a circular rapid transit route within the Chongqing Metro system that connects multiple key districts in Chongqing, China.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7709f92088190a15ae3638d3b14fb |
completed | April 9, 2026, 9:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e2175711d4819088f93bdf64ba4d3f |
completed | April 17, 2026, 11:19 a.m. |
Created at: April 8, 2026, 9:22 p.m.