Triple
T26417265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol – B0026745-02 |
E664130
|
entity |
| Predicate | producerLabelCode |
P175300
|
FINISHED |
| Object | Capitol |
—
|
NE NERFINISHED |
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: Capitol | Statement: [Capitol – B0026745-02, producerLabelCode, Capitol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producerLabelCode Context triple: [Capitol – B0026745-02, producerLabelCode, Capitol]
-
A.
producerOnLabel
Indicates that a producer is credited on or associated with a particular record label.
-
B.
producerLabelAssociation
Indicates that a producer is associated with a particular label, such as a record label, brand, or organizational imprint.
-
C.
productionCode
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.
-
D.
manufacturerCode
Indicates the unique code assigned by a manufacturer to identify a specific product, component, or item it produces.
-
E.
catalogCode
Indicates that an entity is assigned a specific catalog identifier or code used for classification or reference.
- F. None of above. chosen
Provenance (4 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 26, 2026, 11:41 p.m.