Triple
T23949697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chile national transport system |
E603010
|
entity |
| Predicate | notableFerryRoute |
P1737
|
FINISHED |
| Object | Chiloé Island services |
—
|
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: Chiloé Island services | Statement: [Chile national transport system, notableFerryRoute, Chiloé Island services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFerryRoute Context triple: [Chile national transport system, notableFerryRoute, Chiloé Island services]
-
A.
ferryRouteName
Indicates the specific name assigned to a ferry route that connects two or more locations.
-
B.
isOneOfMainCarFerryRoutesTo
Indicates that something serves as one of the primary car ferry routes leading to a specified destination.
-
C.
hasFerryService
chosen
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
D.
notableShipOnRoute
Indicates that a particular ship is especially significant or prominent among those operating on a given route.
-
E.
bodyOfWaterCrossedByFerry
Indicates that a body of water is traversed or crossed by a ferry service.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d03140f08190b4356626628ff56f |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:19 p.m.