Triple
T24460431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadric Malone |
E616802
|
entity |
| Predicate | usedAsCreditOn |
P156192
|
FINISHED |
| Object | Duke Records releases |
—
|
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: Duke Records releases | Statement: [Deadric Malone, usedAsCreditOn, Duke Records releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCreditOn Context triple: [Deadric Malone, usedAsCreditOn, Duke Records releases]
-
A.
creditsUse
Indicates that one entity uses or relies on credits (such as credit units, credit lines, or credit-based resources) provided or available to it.
-
B.
hasCredit
Indicates that an entity possesses or is assigned a credit, such as financial credit, academic credit, or acknowledgment for a contribution.
-
C.
includesCreditTo
Indicates that one entity explicitly acknowledges or attributes credit to another entity, typically for contribution, authorship, or source.
-
D.
hasAlternativeCredit
Indicates that an entity is associated with a different or substitute form of credit or credit option than the primary one.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
- 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298c9956481909f01b51615546807 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:19 a.m.