Triple
T4170602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Unearthly Child |
E84551
|
entity |
| Predicate | serialCode |
P45885
|
FINISHED |
| Object | A |
—
|
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: A | Statement: [An Unearthly Child, serialCode, A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serialCode Context triple: [An Unearthly Child, serialCode, A]
-
A.
serialNumber
Indicates a unique identifying code assigned to an individual item or instance within a series or batch.
-
B.
productionCode
chosen
Indicates the unique identifier or code assigned to a specific production (such as a film, TV episode, or manufactured item) that links related records or versions of that production.
-
C.
manufacturerCode
Indicates the unique code assigned by a manufacturer to identify a specific product, component, or item it produces.
-
D.
catalogCode
Indicates that an entity is assigned a specific catalog identifier or code used for classification or reference.
-
E.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02c87cc88190a9ec3712db18a8a7 |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.