Triple
T38068587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boom Tube |
E950534
|
entity |
| Predicate | firstAssociatedWithCreator |
P32436
|
FINISHED |
| Object | Jack Kirby |
E58705
|
NE 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: Jack Kirby | Statement: [Boom Tube, firstAssociatedWithCreator, Jack Kirby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAssociatedWithCreator Context triple: [Boom Tube, firstAssociatedWithCreator, Jack Kirby]
-
A.
firstCreatorRole
Indicates the specific role or capacity in which the primary or earliest creator of an entity contributed to its creation.
-
B.
associatedWithGenreCreator
Indicates a relationship where a genre is linked to the person or entity that created or originated it.
-
C.
originallyAssociatedWith
chosen
Indicates that an entity was first linked, connected, or affiliated with another entity before any later changes in association.
-
D.
relatedWorkCreator
Indicates that the creator of one work is related (e.g., by authorship, contribution, or collaboration) to the creation of another work.
-
E.
associatedActOfCreator
Indicates a relationship where an act is linked to the creator responsible for or connected with that act.
- F. None of above.
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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d3f601081909098f84ec841dcaa |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.