Triple
T21977928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navlakhi Port |
E542758
|
entity |
| Predicate | navigationChannelType |
P138872
|
FINISHED |
| Object | tidal creek |
—
|
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: tidal creek | Statement: [Navlakhi Port, navigationChannelType, tidal creek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationChannelType Context triple: [Navlakhi Port, navigationChannelType, tidal creek]
-
A.
navigationType
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
-
B.
channelCategory
chosen
Indicates that a channel belongs to or is classified under a particular category.
-
C.
channels
Indicates that one entity serves as a medium, route, or conduit through which another entity is directed, transmitted, or delivered.
-
D.
typicalChannel
Indicates the usual or most commonly used communication or distribution channel through which an interaction, message, or transaction typically occurs.
-
E.
navigationSignals
Indicates that an entity provides or emits signals used to guide or control the movement or navigation of another entity.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1248a60708190a9aa8b9b7738c261 |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:03 p.m.