Triple
T5026618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulder Canyon Project |
E113190
|
entity |
| Predicate | legislativeActYear |
P39113
|
FINISHED |
| Object | 1928 |
—
|
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: 1928 | Statement: [Boulder Canyon Project, legislativeActYear, 1928]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeActYear Context triple: [Boulder Canyon Project, legislativeActYear, 1928]
-
A.
legislatedOn
Indicates that a legislative body has formally considered, debated, or enacted laws or regulations concerning a particular subject or entity.
-
B.
currentLegislatureStartYear
Indicates the calendar year in which the currently serving legislature (or legislative term) officially began.
-
C.
yearEnteredIntoForce
chosen
Indicates the year in which an agreement, law, treaty, or similar instrument officially became legally effective or operational.
-
D.
amendmentYear
Indicates the year in which an amendment to a law, document, or agreement was formally made or enacted.
-
E.
yearOfPromulgation
Indicates the specific year in which something, typically a law or formal decree, was officially enacted or put into effect.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd738c3aac81908fb6a5c70c97a394 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.