Triple
T14237740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Custard Records |
E352929
|
entity |
| Predicate | roleOfFounder |
P5394
|
FINISHED |
| Object | songwriter |
—
|
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: songwriter | Statement: [Custard Records, roleOfFounder, songwriter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfFounder Context triple: [Custard Records, roleOfFounder, songwriter]
-
A.
founderRole
Indicates that an entity serves as a founder in relation to another entity, specifying the role or capacity in which they established it.
-
B.
foundingRole
chosen
Indicates the specific role or capacity an entity held in the founding or establishment of another entity.
-
C.
founder
Indicates that an entity established, created, or started another entity such as an organization, institution, or company.
-
D.
founderTitle
Indicates the formal role or title held by a person in their capacity as a founder of an organization or entity.
-
E.
coFounderOfFounder
Indicates that one entity is a co-founder of another entity who is themselves a founder of something else.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62422e28819089e7115052a28c96 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:08 a.m.