Triple
T3130948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organix |
E65410
|
entity |
| Predicate | hasMemberContribution |
P30146
|
FINISHED |
| Object | Black Thought – 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: Black Thought – vocals | Statement: [Organix, hasMemberContribution, Black Thought – vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberContribution Context triple: [Organix, hasMemberContribution, Black Thought – vocals]
-
A.
hasContributionFrom
chosen
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
B.
hasContributorProgram
Indicates that an entity operates or participates in a formal program through which contributors can submit work, content, or support.
-
C.
hasSupporter
Indicates that one entity supports, endorses, or backs another entity.
-
D.
hasAssociateMember
Indicates that an entity has another entity connected to it in a non-full, typically limited or secondary, membership capacity.
-
E.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada54b0e688190b691771f17f4c721 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.