Triple
T37051069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War (song) |
E917048
|
entity |
| Predicate | associatedLabelImprint |
P49200
|
FINISHED |
| Object | Gordy |
E1005205
|
NE 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: Gordy | Statement: [War (song), associatedLabelImprint, Gordy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLabelImprint Context triple: [War (song), associatedLabelImprint, Gordy]
-
A.
associatedLabelOrImprint
chosen
Indicates a relationship where one entity serves as the label or imprint formally linked to, or published in association with, another entity.
-
B.
recordLabelImprint
Indicates that one record label functions as an imprint (a subsidiary or brand) of another record label.
-
C.
imprintedOn
Indicates that one entity has formed a strong, often early-life, attachment or bond to another entity, typically treating it as a primary reference or caregiver.
-
D.
includesImprint
Indicates that one entity contains, incorporates, or carries the imprint or branding of another entity.
-
E.
ownedLabel
Indicates that a label is possessed or controlled by a particular owner or entity.
- F. None of above.
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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e8c4abdac819095e2335a1adc4cf9 |
completed | June 26, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.