Triple
T14239051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EEE |
E352959
|
entity |
| Predicate | productionCodeType |
P45885
|
FINISHED |
| Object | internal production code |
—
|
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: internal production code | Statement: [EEE, productionCodeType, internal production code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionCodeType Context triple: [EEE, productionCodeType, internal production code]
-
A.
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.
-
B.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
C.
designCode
Indicates that one entity creates, specifies, or defines the design or coding scheme used by another entity.
-
D.
manufacturerCode
Indicates the unique code assigned by a manufacturer to identify a specific product, component, or item it produces.
-
E.
labelCodeType
Indicates that one entity serves as the type or classification scheme for the labeling code applied to 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_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.