Triple
T2869557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian River Lagoon |
E63525
|
entity |
| Predicate | typeOfEstuary |
P15315
|
FINISHED |
| Object | barrier island lagoon system |
—
|
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: barrier island lagoon system | Statement: [Indian River Lagoon, typeOfEstuary, barrier island lagoon system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEstuary Context triple: [Indian River Lagoon, typeOfEstuary, barrier island lagoon system]
-
A.
hasEstuaryType
chosen
Indicates the specific type or classification of an estuary associated with a given water body or location.
-
B.
estuaryName
Indicates the naming relationship that assigns a specific name to an estuary.
-
C.
hasEstuaryNear
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
D.
formsEstuary
Indicates that a river or watercourse meets a larger body of water in such a way that it creates or constitutes an estuary.
-
E.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfe15ff081908dd1dad62c292b2b |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.