Triple
T566171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Lord |
E13556
|
entity |
| Predicate | statusInCanon |
P3927
|
FINISHED |
| Object | often considered extinct after the Time War |
—
|
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: often considered extinct after the Time War | Statement: [Time Lord, statusInCanon, often considered extinct after the Time War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInCanon Context triple: [Time Lord, statusInCanon, often considered extinct after the Time War]
-
A.
canonicalStatus
chosen
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
B.
hasClosedCanon
Indicates that a body of authoritative texts is considered complete and no additional works can be added to it.
-
C.
inCanonOf
Indicates that one entity is officially recognized as part of the established canon or authoritative body of works associated with another entity.
-
D.
canonizedAs
Indicates that an authority, typically a religious institution, has formally declared someone to be a saint or holy figure.
-
E.
canonizedBy
Indicates that an entity has been officially declared a saint or holy figure by a specified religious authority.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b01aca48190944408d066519149 |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c183b081909304944aa3d0fe8f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.