Triple
T14240358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Master (Doctor Who) |
E352985
|
entity |
| Predicate | signatureMethod |
P91204
|
FINISHED |
| Object | disguise |
—
|
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: disguise | Statement: [The Master (Doctor Who), signatureMethod, disguise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureMethod Context triple: [The Master (Doctor Who), signatureMethod, disguise]
-
A.
signatureType
Indicates the specific kind or category of a signature associated with an entity or action.
-
B.
signatureElement
Indicates that one entity is a component or part of another entity’s signature, such as a defining element within a formal or identifying representation.
-
C.
signatureComputation
chosen
Indicates the process or method by which a signature (such as a cryptographic or digital signature) is generated from given input data.
-
D.
signatureBehavior
Indicates a characteristic or distinctive pattern of behavior that uniquely identifies or typifies an entity.
-
E.
signatureVariant
Indicates that one signature is an alternative or modified form of another signature, differing in some aspect such as content, format, or representation while remaining related.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62432fb48190b153805b85c4f2d2 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:08 a.m.