Triple
T33226539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silas Adams (Deadwood) |
E850567
|
entity |
| Predicate | originalNetworkRunEnd |
P203950
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Silas Adams (Deadwood), originalNetworkRunEnd, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNetworkRunEnd Context triple: [Silas Adams (Deadwood), originalNetworkRunEnd, 2006]
-
A.
originalRunEndNetwork
Indicates the network or system in which an original run, process, or sequence ultimately concludes or terminates.
-
B.
originalNetworkRunStart
Indicates the time or event at which a network process, operation, or run was first initiated.
-
C.
originalNetworkRunStatus
Indicates the execution or operational status of the network as it was in its original or initial run configuration.
-
D.
originalRunStartNetwork
Indicates the network on which a program or series first began its original broadcast run.
-
E.
originalRunEndOfWork
Indicates that a given run or process marks the final or concluding point of a particular piece of work.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a02fcbe03d0819082d3dd715ed41623 |
completed | May 12, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_6a02fc62138081908d2dbc5db7541d13 |
completed | May 12, 2026, 10:09 a.m. |
| PDg | Predicate description generation | batch_6a02fcbd67c8819089827d38434063a1 |
completed | May 12, 2026, 10:11 a.m. |
Created at: May 1, 2026, 1:30 a.m.