Triple
T516794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guayas River |
E10725
|
entity |
| Predicate | hasEstuaryType |
P15315
|
FINISHED |
| Object | tidal estuary |
—
|
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 estuary | Statement: [Guayas River, hasEstuaryType, tidal estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstuaryType Context triple: [Guayas River, hasEstuaryType, tidal estuary]
-
A.
hasMarineEcosystem
Indicates that an entity possesses, contains, or is associated with a marine ecosystem as part of its characteristics or environment.
-
B.
hasWaterwayRole
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
-
C.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
D.
hasFloodplain
Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
-
E.
hasHydrologicalFunction
Indicates that something performs a role or action related to the movement, storage, or regulation of water within a hydrological system.
- F. None of above. chosen
Provenance (4 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f184c3a481909bf60bb627b0ea88 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f1137e948190838303cdaa757a5a |
completed | Feb. 28, 2026, 1:43 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.