Triple
T27642014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jupiter's Legacy |
E696611
|
entity |
| Predicate | laterCollectedAs |
P180317
|
FINISHED |
| Object | trade paperbacks |
—
|
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: trade paperbacks | Statement: [Jupiter's Legacy, laterCollectedAs, trade paperbacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCollectedAs Context triple: [Jupiter's Legacy, laterCollectedAs, trade paperbacks]
-
A.
collectedAs
Indicates that one entity has been gathered, acquired, or assembled as part of another entity, such as a collection, set, or group.
-
B.
collectionLaterBecame
chosen
Indicates that one collection was transformed into, reclassified as, or otherwise evolved into another collection at a later time.
-
C.
collectedSince
Indicates that one entity has been continuously collecting or accumulating another entity starting from a specified point in time.
-
D.
collectedWith
Indicates that one entity was gathered, acquired, or obtained together with another entity as part of the same collection event or process.
-
E.
collectedThrough
Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 27, 2026, 2:27 p.m.