Triple
T23731407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stone Cold Gentleman |
E586417
|
entity |
| Predicate | performerAssociation |
P46749
|
FINISHED |
| Object | New Edition |
—
|
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: New Edition | Statement: [Stone Cold Gentleman, performerAssociation, New Edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerAssociation Context triple: [Stone Cold Gentleman, performerAssociation, New Edition]
-
A.
associatedWithPerformer
chosen
Indicates a relationship in which something (such as a work, event, or role) is connected or linked to a specific performer.
-
B.
associatedPerformerPersona
Indicates a relationship where a performer is linked to a specific persona or role identity they adopt in their performances.
-
C.
performerMemberOf
Indicates that a performer is a member of, or affiliated with, a particular group, organization, or ensemble.
-
D.
performerRelationshipContext
Indicates the contextual nature or circumstances of the relationship between a performer and another entity (such as an event, work, or role).
-
E.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b9193b14819096f1c7b11a441569 |
completed | April 29, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:09 p.m.