Triple
T31926667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney–Lucasfilm Press |
E815131
|
entity |
| Predicate | publishesForUniverse |
P18285
|
FINISHED |
| Object | Star Wars canon |
—
|
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: Star Wars canon | Statement: [Disney–Lucasfilm Press, publishesForUniverse, Star Wars canon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishesForUniverse Context triple: [Disney–Lucasfilm Press, publishesForUniverse, Star Wars canon]
-
A.
publishesFor
Indicates that one entity issues, releases, or makes content publicly available on behalf of, or in service of, another entity.
-
B.
publisherInUniverse
chosen
Indicates that a publisher operates, exists, or is recognized within a particular fictional or conceptual universe.
-
C.
inUniversePublicationType
Indicates that a publication exists within the fictional universe itself (diegetic) and specifies what type of in-universe publication it is.
-
D.
publishesTo
Indicates that one entity distributes, releases, or makes content available to another entity or destination.
-
E.
alsoPublishes
Indicates that an entity, in addition to its primary publishing activity, publishes another type of content, work, or medium as well.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 1, 2026, 12:03 a.m.