Triple
T5095272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pathé |
E114849
|
entity |
| Predicate | recordLabelActivePeriod |
P60712
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Pathé, recordLabelActivePeriod, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordLabelActivePeriod Context triple: [Pathé, recordLabelActivePeriod, early 20th century]
-
A.
recordLabelFounded
Indicates that a particular record label was established or created by a specific founder or founding entity.
-
B.
hasRecordLabel
Indicates that an entity (typically a musical artist or release) is associated with or signed to a particular record label.
-
C.
recordStartYear
Indicates the calendar year in which a particular record, entry, or data instance first began or was created.
-
D.
ownedRecordLabel
Indicates that one entity previously possessed legal ownership or controlling interest in a particular record label.
-
E.
liveAlbumRecordingDates
Indicates the specific dates on which the live album’s performances were recorded.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7563ad608190879a26a0bf07c3f6 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd72b8d7a88190ad53fae64f17e22c |
completed | March 20, 2026, 4:15 p.m. |
Created at: March 20, 2026, 1:40 p.m.