Triple
T18436943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whangārei Harbour |
E450416
|
entity |
| Predicate | hasInletType |
P23365
|
FINISHED |
| Object | drowned river valley |
—
|
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: drowned river valley | Statement: [Whangārei Harbour, hasInletType, drowned river valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInletType Context triple: [Whangārei Harbour, hasInletType, drowned river valley]
-
A.
hasInlet
chosen
Indicates that one entity serves as an inlet or entry point through which another entity receives a flow of material, energy, or fluid.
-
B.
hasPortType
Indicates that an entity is associated with, or characterized by, a specific type or category of port.
-
C.
hasFlowType
Indicates the type or category of flow associated with or exhibited by an entity.
-
D.
hasJunctionType
Indicates the specific kind or classification of a junction associated with an entity.
-
E.
hasParameterType
Indicates that a parameter in a function, method, or operation is associated with a specific data type.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c0e04508190bc851a8954ae60e8 |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:29 a.m.