Triple
T16315835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24 Season 7 |
E396170
|
entity |
| Predicate | usesNarrativeFormat |
P35682
|
FINISHED |
| Object | real-time format |
—
|
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: real-time format | Statement: [24 Season 7, usesNarrativeFormat, real-time format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNarrativeFormat Context triple: [24 Season 7, usesNarrativeFormat, real-time format]
-
A.
usesNarrativeStyle
Indicates that one entity employs or adopts a particular narrative style in presenting or structuring content or information.
-
B.
narrativeFormat
chosen
Indicates the specific structural or stylistic form in which a narrative is presented or expressed.
-
C.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
D.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
E.
supportsNarrativeText
Indicates that one entity provides justification, evidence, or contextual backing that helps explain or validate the narrative content expressed by another entity.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b1e9988190a1dce9f1ed7031df |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.