Triple
T13747640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Featured vocals by Ant Clemons |
E330256
|
entity |
| Predicate | creditRole |
P51151
|
FINISHED |
| Object | vocals |
—
|
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: vocals | Statement: [Featured vocals by Ant Clemons, creditRole, vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creditRole Context triple: [Featured vocals by Ant Clemons, creditRole, vocals]
-
A.
carbonRole
Indicates the functional role or involvement that an entity has in relation to carbon within a given process, system, or context.
-
B.
roleInCollateral
Indicates that an entity participates in or is assigned a specific role within a collateral arrangement or structure.
-
C.
creditFunction
Indicates a financial role or operation through which an entity extends, manages, or utilizes credit within an economic or transactional context.
-
D.
effectiveRole
chosen
Indicates the functional role or capacity an entity actually performs or holds in a given context, regardless of its formal or nominal designation.
-
E.
creditsCanBe
Indicates that certain credits are permitted to be in a specified state, category, or usage condition.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02132a108190aca728b95e83af01 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:08 p.m.