Triple
T32142680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quality Comics |
E820946
|
entity |
| Predicate | assetsAcquiredBy |
P22682
|
FINISHED |
| Object | DC 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: DC Comics | Statement: [Quality Comics, assetsAcquiredBy, DC Comics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assetsAcquiredBy Context triple: [Quality Comics, assetsAcquiredBy, DC Comics]
-
A.
acquiredFor
Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third entity.
-
B.
couldBeAcquiredBy
Indicates that one entity is a potential target to be obtained, bought, or taken over by another entity.
-
C.
acquiredWith
Indicates that one entity was obtained, purchased, or gained together with or by means of another entity.
-
D.
laterAcquiredBy
chosen
Indicates that one entity was acquired by another entity at a later point in time, after some prior state or ownership.
-
E.
wasAcquiredIn
Indicates that one entity obtained ownership or control of another entity through an acquisition event that occurred at a specific time or in a specific transaction.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9af93e081908d003dd45258ad27 |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:31 a.m.