Triple
T23461825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nauta |
E568998
|
entity |
| Predicate | riverPortFunction |
P30340
|
FINISHED |
| Object | embarkation point for Amazon cruises |
—
|
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: embarkation point for Amazon cruises | Statement: [Nauta, riverPortFunction, embarkation point for Amazon cruises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverPortFunction Context triple: [Nauta, riverPortFunction, embarkation point for Amazon cruises]
-
A.
waterwayFunction
chosen
Indicates the primary role or purpose that a waterway serves, such as transportation, irrigation, drainage, or recreation.
-
B.
eraOfMajorUseAsFerryTerminal
Indicates the time period during which a location was primarily used as a ferry terminal.
-
C.
connectsToRiverPort
Indicates that one location, route, or infrastructure element has a direct linkage or access to a river port.
-
D.
hasRiverPortPotential
Indicates that a location has suitable conditions to support the development or operation of a river port.
-
E.
waterTransport
Indicates the movement or conveyance of something from one place to another via water-based means such as rivers, seas, or other aquatic routes.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a69bc200819096ed2baf25cdee4f |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.