Triple
T4336058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Channeled Scablands |
E97465
|
entity |
| Predicate | proposalYearByBretz |
P25813
|
FINISHED |
| Object | 1923 |
—
|
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: 1923 | Statement: [Channeled Scablands, proposalYearByBretz, 1923]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposalYearByBretz Context triple: [Channeled Scablands, proposalYearByBretz, 1923]
-
A.
proposedInYear
chosen
Indicates that something, such as a plan, idea, or piece of legislation, was formally put forward or suggested in a specific calendar year.
-
B.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
-
C.
promotionYear
Indicates the year in which an entity was promoted to a new position, rank, or status.
-
D.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
E.
recastInYear
Indicates that an existing work, role, or production was cast again with different performers in a specified year.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3516af43081908393fd0dad3d9382 |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:14 p.m.