Triple
T2089930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent Records |
E32643
|
entity |
| Predicate | successorLabel |
P34641
|
FINISHED |
| Object | reissue labels using the Kent name |
—
|
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: reissue labels using the Kent name | Statement: [Kent Records, successorLabel, reissue labels using the Kent name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorLabel Context triple: [Kent Records, successorLabel, reissue labels using the Kent name]
-
A.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
B.
symbolForSuccessor
Indicates that one entity serves as the symbolic representation or notation of the successor (the next element) of another entity in a sequence or structure.
-
C.
successorInPractice
Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
-
D.
successorCategory
Indicates that one category directly follows or replaces another in an ordered sequence or hierarchy.
-
E.
successorLine
Indicates that one line directly follows another in a sequence or ordered arrangement.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba730a5c8190a85be72149574d79 |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b4356881909217c42ccb8bb1ed |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:43 p.m.