Triple
T3697532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamsui River |
E78493
|
entity |
| Predicate | hasEstuaryFeature |
P6651
|
FINISHED |
| Object | tidal influence |
—
|
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 influence | Statement: [Tamsui River, hasEstuaryFeature, tidal influence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstuaryFeature Context triple: [Tamsui River, hasEstuaryFeature, tidal influence]
-
A.
hasEstuaryType
Indicates the specific type or classification of an estuary associated with a given water body or location.
-
B.
hasEstuaryNear
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
C.
estuaryName
Indicates the naming relationship that assigns a specific name to an estuary.
-
D.
hasShoreFeature
chosen
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
E.
containsCoastalFeature
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc5115ad8819085ffa938de3943f4 |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.