Triple
T23830001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B.B. King and his band |
E589486
|
entity |
| Predicate | activeWithLeader |
P153775
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [B.B. King and his band, activeWithLeader, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeWithLeader Context triple: [B.B. King and his band, activeWithLeader, mid-20th century]
-
A.
servedUnderLeader
Indicates that one entity held a position or role subordinate to, and operating under the authority or command of, another specified leader.
-
B.
implementedUnderLeader
Indicates that an action, project, or policy was carried out under the authority, direction, or tenure of a specific leader.
-
C.
establishedUnderLeader
Indicates that an entity was founded, created, or formally established during the tenure or authority of a specific leader.
-
D.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
E.
supportedLeader
Indicates that one entity actively backed, endorsed, or provided assistance to a particular leader.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f498c48190827e59df868c5cb1 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f158b0e320819090b947ee7eb14116 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 17, 2026, 8:01 p.m.