Triple
T9496243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kissimmee River basin |
E229011
|
entity |
| Predicate | historicalModification |
P88939
|
FINISHED |
| Object | channelization of Kissimmee River |
—
|
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: channelization of Kissimmee River | Statement: [Kissimmee River basin, historicalModification, channelization of Kissimmee River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalModification Context triple: [Kissimmee River basin, historicalModification, channelization of Kissimmee River]
-
A.
historicalRecord
Indicates that there exists a documented account or record capturing information about an entity, event, or relationship from the past.
-
B.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
C.
historicalVersion
Indicates that one entity represents an earlier or past version in the history or evolution of another entity.
-
D.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
E.
historicalField
Indicates that one entity’s field of study, work, or relevance is situated within the historical domain or concerns past events.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd95eb87b081908fc7255598cd9a24 |
completed | April 1, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca8c6b0f081908334d6c7cf80e03c |
completed | April 1, 2026, 5:10 a.m. |
Created at: March 30, 2026, 7:56 p.m.