Triple
T27309599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jules Taub |
E689164
|
entity |
| Predicate | usedInCollaborationWith |
P179470
|
FINISHED |
| Object | B.B. King |
—
|
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: B.B. King | Statement: [Jules Taub, usedInCollaborationWith, B.B. King]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCollaborationWith Context triple: [Jules Taub, usedInCollaborationWith, B.B. King]
-
A.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
B.
usedToOperateInConjunctionWith
Indicates that one entity was formerly operated together with another entity as part of a combined or coordinated functioning.
-
C.
implementedInCooperationWith
Indicates that an action, project, or initiative was carried out jointly or collaboratively together with another party.
-
D.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
usesCollaboration
Indicates that one entity employs or relies on collaborative methods, tools, or partnerships with another entity to achieve a shared goal or perform an activity.
- 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_69ef355b931c8190a63cafaf7bcc008b |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 27, 2026, 11:27 a.m.