Triple
T23960133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Digue jetty at La Passe |
E603901
|
entity |
| Predicate | isMainFerryLandingPointFor |
P15716
|
FINISHED |
| Object | La Digue Island |
—
|
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: La Digue Island | Statement: [La Digue jetty at La Passe, isMainFerryLandingPointFor, La Digue Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainFerryLandingPointFor Context triple: [La Digue jetty at La Passe, isMainFerryLandingPointFor, La Digue Island]
-
A.
hasFerryPort
chosen
Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
-
B.
eraOfMajorUseAsFerryTerminal
Indicates the time period during which a location was primarily used as a ferry terminal.
-
C.
hasNearbyFerryPort
Indicates that one location is situated close enough to another location that serves as a ferry port to be considered nearby.
-
D.
isOneOfMainCarFerryRoutesTo
Indicates that something serves as one of the primary car ferry routes leading to a specified destination.
-
E.
linkedByFerryTo
Indicates that one place is connected to another by a ferry route that enables transport between them.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0da04cc8190a8d55512d4c7efdd |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:23 p.m.