Triple
T2853741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehama-Colusa Canal |
E63150
|
entity |
| Predicate | projectAuthorityEstablished |
P17950
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Tehama-Colusa Canal, projectAuthorityEstablished, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectAuthorityEstablished Context triple: [Tehama-Colusa Canal, projectAuthorityEstablished, 1990s]
-
A.
establishesOrgan
Indicates that an entity creates, founds, or sets up an organization or institutional body.
-
B.
designatesAuthority
Indicates that one entity formally assigns or confers decision-making power or control over something to another entity.
-
C.
constructionAuthority
chosen
Indicates that an entity has the official power or responsibility to oversee, approve, or manage construction-related activities for another entity or project.
-
D.
governingBodyEstablished
Indicates that a particular governing body was formally created or brought into existence for an entity or domain.
-
E.
designationAuthority
Indicates the entity that has the official power or responsibility to assign, grant, or confer a particular designation to another entity.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf5f21348190a574fa86bc71c76f |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.