Triple
T30401797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars: The High Republic |
E773368
|
entity |
| Predicate | initialAnnouncementName |
P179820
|
FINISHED |
| Object | Project Luminous |
—
|
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: Project Luminous | Statement: [Star Wars: The High Republic, initialAnnouncementName, Project Luminous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialAnnouncementName Context triple: [Star Wars: The High Republic, initialAnnouncementName, Project Luminous]
-
A.
mainAnnouncement
Indicates that something serves as the primary or most important announcement in a given context or collection of announcements.
-
B.
primaryAnnouncer
Indicates that an entity serves as the main or lead announcer in a given event, program, or context.
-
C.
announcedAs
Indicates that one entity is publicly presented, declared, or introduced in a specified role, name, or capacity by another entity.
-
D.
standardAnnounced
Indicates that an official standard has been formally announced or made public.
-
E.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
- F. None of above. chosen
Provenance (4 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: April 29, 2026, 8:03 p.m.