Triple
T21181830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Galaxy Being |
E521969
|
entity |
| Predicate | hasOpeningControlVoiceMonologue |
P143199
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Galaxy Being, hasOpeningControlVoiceMonologue, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningControlVoiceMonologue Context triple: [The Galaxy Being, hasOpeningControlVoiceMonologue, yes]
-
A.
hasDialogueTrait
Indicates that an entity possesses a specific characteristic or quality related to dialogue or conversational behavior.
-
B.
hasDialogueIn
Indicates that an entity participates in or contains spoken or written dialogue within a specified context, such as a scene, work, or medium.
-
C.
hasOpeningScene
Indicates that a work (such as a film, show, or story) possesses a specific initial scene that begins or introduces its narrative.
-
D.
hasDialogueSystem
Indicates that an entity includes or is equipped with a system for managing dialogue or conversational interactions.
-
E.
hasOpeningSceneArgumentAbout
Indicates that the opening scene of a work features an argument involving the specified entities.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7301eb3248190b9f6fc1586651fec |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:01 p.m.