Triple
T13891644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intercidades |
E333984
|
entity |
| Predicate | route |
P5619
|
FINISHED |
| Object | Lisbon–Faro |
E971741
|
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: Lisbon–Faro | Statement: [Intercidades, route, Lisbon–Faro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lisbon–Faro Context triple: [Intercidades, route, Lisbon–Faro]
-
A.
Lisbon–Faro
chosen
Lisbon–Faro is a major intercity rail corridor in Portugal linking the capital Lisbon with the southern coastal city of Faro in the Algarve region.
-
B.
Porto–Faro
Porto–Faro is a major long-distance rail route in Portugal linking the northern city of Porto with the southern Algarve city of Faro.
-
C.
Lisbon–Guimarães
Lisbon–Guimarães is a major intercity rail route in Portugal connecting the capital Lisbon with the historic northern city of Guimarães.
-
D.
Lisbon–Beja
Lisbon–Beja is a long-distance Intercidades rail service in Portugal connecting the capital city Lisbon with the inland city of Beja.
-
E.
Lisbon–Covilhã
Lisbon–Covilhã is a long-distance Intercidades rail service in Portugal connecting the capital city Lisbon with the inland city of Covilhã across the country’s central region.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a537d4819093c2bae2a244816a |
completed | April 14, 2026, 11:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb649c12c819086e85d1dc49624f1 |
completed | May 7, 2026, 3:56 p.m. |
Created at: April 9, 2026, 10:15 p.m.