Triple
T22800572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allido Records |
E564377
|
entity |
| Predicate | labelFounderOccupation |
P97851
|
FINISHED |
| Object | record producer |
—
|
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: record producer | Statement: [Allido Records, labelFounderOccupation, record producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelFounderOccupation Context triple: [Allido Records, labelFounderOccupation, record producer]
-
A.
labelFounder
Indicates that one entity is the founder or creator of another entity, such as an organization, project, or initiative.
-
B.
labelFounderProducer
Indicates that an entity is the founder or originator responsible for producing or creating another entity.
-
C.
notableCoFounderOccupation
Indicates that the co-founder is particularly notable or recognized for having a specific occupation.
-
D.
associatedProfessionOfFounder
chosen
Indicates the professional field or occupation linked to the founder of an entity.
-
E.
foundedByOccupation
Indicates that an entity (such as an organization or institution) was founded by a person or group characterized by a specific occupation or professional role.
- F. None of above.
Provenance (3 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cdc72908190827c9e36a498dc97 |
completed | April 29, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:31 p.m.