Triple
T24296571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tattingers |
E605972
|
entity |
| Predicate | hasOriginalRunType |
P85647
|
FINISHED |
| Object | Primetime network television series |
—
|
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: Primetime network television series | Statement: [Tattingers, hasOriginalRunType, Primetime network television series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalRunType Context triple: [Tattingers, hasOriginalRunType, Primetime network television series]
-
A.
originalRunType
chosen
Indicates the initial or primary category or mode under which a particular run, execution, or process was originally conducted.
-
B.
hasRunType
Indicates the type or category of a run associated with an entity (e.g., execution mode, run classification, or run configuration).
-
C.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
D.
originalRunStatus
Indicates the initial or prior execution state of a run before any subsequent updates or changes.
-
E.
showOriginalRunStart
Indicates that the original or initial start time of a run, process, or execution should be displayed.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f2915a00f08190a93a009ada096b69 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.