Triple
T28948699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red River Floodway |
E730947
|
entity |
| Predicate | expansionCompletedIn |
P60942
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Red River Floodway, expansionCompletedIn, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionCompletedIn Context triple: [Red River Floodway, expansionCompletedIn, 2010]
-
A.
laterExpansionCompletion
Indicates that the completion of an expansion occurs at a later time than another referenced event or expansion.
-
B.
expansionStatus
Indicates the current state or phase of growth, enlargement, or extension of something relative to its previous or intended size or scope.
-
C.
completionOf
Indicates that one entity represents the finished state, fulfillment, or successful conclusion of another entity, process, or requirement.
-
D.
expansionCompletion
chosen
Indicates that a previously initiated expansion process or enlargement of something has been fully completed.
-
E.
wasExpandedIn
Indicates that something increased in size, scope, or extent during a specified time or event.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 8:42 a.m.