Triple
T36882954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roteiro de Lisboa a Goa |
E911529
|
entity |
| Predicate | describesRoute |
P20574
|
FINISHED |
| Object | Lisbon–Goa sea route |
—
|
NE NERFINISHED |
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–Goa sea route | Statement: [Roteiro de Lisboa a Goa, describesRoute, Lisbon–Goa sea route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesRoute Context triple: [Roteiro de Lisboa a Goa, describesRoute, Lisbon–Goa sea route]
-
A.
routeDescription
chosen
Indicates a textual explanation or summary of the path, course, or itinerary taken between locations.
-
B.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
C.
routeDetail
Indicates the specific characteristics or parameters of a route, such as its path, segments, or configuration details, within a routing relationship.
-
D.
servesAsRouteTo
Indicates that one entity functions as a pathway, channel, or means of access leading to another entity.
-
E.
routeDesignationOf
Indicates that one entity is the official route number, code, or designation assigned to another entity representing a transportation route.
- F. None of above.
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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 3, 2026, 4:13 p.m.