Triple
T6492038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama River |
E148061
|
entity |
| Predicate | stateWaterway |
P71041
|
FINISHED |
| Object | major waterway of Alabama |
—
|
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: major waterway of Alabama | Statement: [Alabama River, stateWaterway, major waterway of Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateWaterway Context triple: [Alabama River, stateWaterway, major waterway of Alabama]
-
A.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
B.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
C.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
D.
waterwayJunction
Indicates a point where two or more waterways meet, intersect, or branch from one another.
-
E.
hasWaterwayRole
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a9bf9208190b0957eda06ed3d65 |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c067f1ef148190bc0355abe83f7e16 |
completed | March 22, 2026, 10:06 p.m. |
Created at: March 22, 2026, 4:53 p.m.