Triple
T37718395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USA Comics #1 |
E939515
|
entity |
| Predicate | publisherPredecessorOf |
P194034
|
FINISHED |
| Object | Marvel Comics |
—
|
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: Marvel Comics | Statement: [USA Comics #1, publisherPredecessorOf, Marvel Comics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherPredecessorOf Context triple: [USA Comics #1, publisherPredecessorOf, Marvel Comics]
-
A.
formerPublisher
Indicates that one entity previously served as the publisher of another entity but no longer holds that role.
-
B.
precedesInPublication
chosen
Indicates that one item is published or released before another in a temporal or sequential order.
-
C.
publisherAtTime
Indicates that a given entity serves as the publisher of another entity during a specified time interval.
-
D.
publisherOfWorkAppearingIn
Indicates that an entity is the publisher responsible for issuing a work in which another specified work appears (e.g., as part of a collection, volume, or compilation).
-
E.
publisherEditor
Indicates a relationship where one entity serves as the editor responsible for the content published by another entity acting as the publisher.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fffc783b648190bcd7df017514d206 |
completed | May 10, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69fffc03fa24819099e12413dc6e0afd |
completed | May 10, 2026, 3:31 a.m. |
Created at: May 3, 2026, 4:18 p.m.