Triple
T24891202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Warrior River system |
E623006
|
entity |
| Predicate | hasMainStem |
P31275
|
FINISHED |
| Object | Black Warrior River |
—
|
NE NERFINISHED |
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: Black Warrior River | Statement: [Black Warrior River system, hasMainStem, Black Warrior River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainStem Context triple: [Black Warrior River system, hasMainStem, Black Warrior River]
-
A.
hasStem
chosen
Indicates that one entity possesses or is characterized by a stem as a structural or functional part.
-
B.
hasMainTrunkLine
Indicates that an entity is connected to or served by a primary or central trunk line within a network or system.
-
C.
hasMainStructure
Indicates that one entity serves as the primary or central structural component of another entity.
-
D.
hasMainStandOn
Indicates that one entity serves as the primary physical support structure or main stand for another entity.
-
E.
hasMainOrgan
Indicates that an entity possesses a primary or principal organ that plays a central role in its biological or functional system.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 18, 2026, 5:26 a.m.