Triple
T28638332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlton Comics |
E724851
|
entity |
| Predicate | notableCharacterPublisherOf |
P117210
|
FINISHED |
| Object | Blue Beetle |
—
|
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: Blue Beetle | Statement: [Charlton Comics, notableCharacterPublisherOf, Blue Beetle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterPublisherOf Context triple: [Charlton Comics, notableCharacterPublisherOf, Blue Beetle]
-
A.
publisherOfNotableWork
Indicates that the subject is the publishing entity responsible for releasing the object, which is a notable or significant work.
-
B.
notableWorkAuthor
Indicates that one entity is the creator or author of a notable work associated with another entity.
-
C.
notableAuthorPublished
Indicates that a work was published by an author who is recognized as notable or distinguished.
-
D.
publisherOfWorksFeaturingCharacter
chosen
Indicates that one entity is the publisher responsible for releasing works in which a given character appears.
-
E.
notableWorkPrintedWith
Indicates that a notable work is physically printed together with, or in association with, another specified item (such as another work, edition, or publication).
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a01487b73488190954eb5143e6f246e |
completed | May 11, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_6a0145210ae481908da59b02efdbc397 |
completed | May 11, 2026, 2:55 a.m. |
Created at: April 28, 2026, 4:42 a.m.