Triple
T27371011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clear Creek (Texas) |
E690318
|
entity |
| Predicate | hasEstuarineCharacteristics |
P117950
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Clear Creek (Texas), hasEstuarineCharacteristics, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstuarineCharacteristics Context triple: [Clear Creek (Texas), hasEstuarineCharacteristics, true]
-
A.
isEstuarine
chosen
Indicates that something is located in, formed in, or characteristic of an estuary, where river and seawater environments meet.
-
B.
hasEstuaryEnvironment
Indicates that something is located in, associated with, or characterized by an estuary environment where river and marine conditions interact.
-
C.
hasEstuaryType
Indicates the specific type or classification of an estuary associated with a given water body or location.
-
D.
hasEstuaryAt
Indicates that a river or watercourse flows into and meets a larger body of water (such as a sea, ocean, or lake) at a specific location.
-
E.
hasEstuaryWith
Indicates that a river or watercourse flows into and forms an estuary with a particular body of water.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62c620cac8190ad616f4f0920c445 |
completed | May 2, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:18 p.m.