Triple
T21955738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergeant Ernest G. Bilko |
E542181
|
entity |
| Predicate | showOriginalRunEnd |
P44889
|
FINISHED |
| Object | 1959 |
—
|
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: 1959 | Statement: [Sergeant Ernest G. Bilko, showOriginalRunEnd, 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showOriginalRunEnd Context triple: [Sergeant Ernest G. Bilko, showOriginalRunEnd, 1959]
-
A.
endOfOriginalRun
chosen
Indicates the point in time or event at which the original run or initial airing of something (such as a series, process, or program) concludes.
-
B.
originalRunEndNetwork
Indicates the network or system in which an original run, process, or sequence ultimately concludes or terminates.
-
C.
originalRunStatus
Indicates the initial or prior execution state of a run before any subsequent updates or changes.
-
D.
originalRunBlock
Indicates that a given block of execution or code is the initial or primary run block from which a process, task, or workflow is originally executed.
-
E.
showOriginalNetwork
Indicates that an entity reveals or specifies the original network or source network from which it originated or was first broadcast.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f124404f38819080bae736a52a51cd |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:59 p.m.