Triple
T30409103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayou Bonne Idee |
E773560
|
entity |
| Predicate | hasWaterFlowCharacteristic |
P137958
|
FINISHED |
| Object | slow-moving waters |
—
|
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: slow-moving waters | Statement: [Bayou Bonne Idee, hasWaterFlowCharacteristic, slow-moving waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterFlowCharacteristic Context triple: [Bayou Bonne Idee, hasWaterFlowCharacteristic, slow-moving waters]
-
A.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
-
B.
hasWaterMovement
chosen
Indicates that one entity exhibits or is characterized by a particular type or pattern of water movement.
-
C.
hasWaterLevelCharacteristic
Indicates that an entity is associated with a specific property, feature, or behavior related to its water level.
-
D.
waterFlowsThrough
Indicates that water moves along a path or channel passing from one location or object to another.
-
E.
hasWaterFunction
Indicates that an entity performs, provides, or is associated with a specific function or role related to 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 8:04 p.m.