Triple
T13084872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thorildsplan |
E310304
|
entity |
| Predicate | line |
P1293
|
FINISHED |
| Object | Green line |
E378322
|
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: Green line | Statement: [Thorildsplan, line, Green line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Green line Context triple: [Thorildsplan, line, Green line]
-
A.
Green line
The Green line is a major rapid transit route on the Barcelona Metro system, serving numerous central and outlying neighborhoods across the city.
-
B.
Green line
chosen
The Green line is one of the main color-coded routes in the Stockholm metro system, serving numerous central and suburban stations across the city.
-
C.
green line
The green line refers to the Zamoskvoretskaya Line, one of the busiest and oldest lines of the Moscow Metro system.
-
D.
Blue line
The Blue line is one of the main lines of the Stockholm metro system, connecting central Stockholm with several northern and western suburbs.
-
E.
Red line
The Red line is one of the main color-coded routes of the Stockholm metro system, serving numerous central and suburban stations across the city.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981361e8c819099376435aa3a7aa3 |
completed | April 10, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d61060188190911eb3e135dc25ac |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 9:02 p.m.