Triple
T38182625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invictus Records |
E1005212
|
entity |
| Predicate | hasSisterLabel |
P197583
|
FINISHED |
| Object | Hot Wax Records |
—
|
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: Hot Wax Records | Statement: [Invictus Records, hasSisterLabel, Hot Wax Records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSisterLabel Context triple: [Invictus Records, hasSisterLabel, Hot Wax Records]
-
A.
hasSisterRelationshipType
Indicates that there exists a sister-type familial relationship between the related entities.
-
B.
hasSister
Indicates that one entity is the sister of another entity.
-
C.
hasSisterProperty
Indicates that one property is related to another as a sister property, typically sharing a common parent or similar hierarchical level.
-
D.
hasSisterOrganization
Indicates that one organization is related to another as a sister organization, typically sharing a common parent, affiliation, or parallel status within the same overarching structure.
-
E.
hasLabel
Indicates that an entity is associated with a specific textual label or name used to identify or describe it.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
| PDg | Predicate description generation | batch_69fe9b013ec481908f89beddb9c4cd4e |
completed | May 9, 2026, 2:25 a.m. |
Created at: May 3, 2026, 4:29 p.m.