Triple
T19284172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Macra Terror |
E482264
|
entity |
| Predicate | episodesMissingFromArchives |
P50201
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [The Macra Terror, episodesMissingFromArchives, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: episodesMissingFromArchives Context triple: [The Macra Terror, episodesMissingFromArchives, 4]
-
A.
hasMissingEpisode
chosen
Indicates that an entity (such as a series or season) is associated with one or more episodes that are absent or not available.
-
B.
hasEpisode
Indicates that something, typically a series or program, includes a specific episode as one of its constituent parts.
-
C.
intendedEpisodes
Indicates that one entity is planned or designated to appear in, be used for, or be associated with specific episodes of another entity (such as a series or program).
-
D.
hasEpisodeList
Indicates that an entity is associated with a collection or sequence of episodes, typically ordered as a list.
-
E.
statusOfOriginalEpisodes
Indicates the current condition, availability, or release state of the original episodes in relation to a work or series.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc0099148190bfec8e8eadc72406 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.