Triple
T26662876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscavide station |
E666696
|
entity |
| Predicate | servesTransportLinks |
P183702
|
FINISHED |
| Object | Lisbon’s eastern transport links |
—
|
LITERAL 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’s eastern transport links | Statement: [Moscavide station, servesTransportLinks, Lisbon’s eastern transport links]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesTransportLinks Context triple: [Moscavide station, servesTransportLinks, Lisbon’s eastern transport links]
-
A.
transportationLinksTo
Indicates that there is a transportation connection or route enabling movement or travel between the two entities.
-
B.
servedByTransportation
Indicates that a location or entity is provided access or connection by a particular mode or service of transportation.
-
C.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
D.
transportLinkType
Indicates the specific kind of transportation connection or route that exists between two locations or transport nodes.
-
E.
hasGoodTransportLinks
Indicates that a place is well connected to other locations by efficient and convenient transport options.
- F. None of above. chosen
Provenance (4 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: April 27, 2026, 2:37 a.m.