Triple
T16505366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chet Baker in Tokyo |
E400912
|
entity |
| Predicate | mainInstrumentOfLeader |
P123814
|
FINISHED |
| Object | trumpet |
—
|
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: trumpet | Statement: [Chet Baker in Tokyo, mainInstrumentOfLeader, trumpet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainInstrumentOfLeader Context triple: [Chet Baker in Tokyo, mainInstrumentOfLeader, trumpet]
-
A.
hadPrincipalLeader
Indicates that an entity was led or headed by a primary or chief leader.
-
B.
coupLeader
Indicates that the subject is the primary organizer or head figure responsible for leading a coup against an existing authority.
-
C.
mainLeaders
Indicates that the referenced entities serve as the primary or most important leaders within a group, organization, or context.
-
D.
unificationLeader
Indicates that one entity serves as the primary leader or guiding figure responsible for unifying or bringing together multiple other entities into a single group or structure.
-
E.
otherMajorLeader
Indicates that one entity is a significant political or organizational leader distinct from the primary or main leader in a given 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e51ce1c81909548298f703a7ffa |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:14 a.m.