Triple
T27810768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millennium Falcon: Smugglers Run |
E702511
|
entity |
| Predicate | storyCharacter |
P45541
|
FINISHED |
| Object | Hondo Ohnaka |
—
|
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: Hondo Ohnaka | Statement: [Millennium Falcon: Smugglers Run, storyCharacter, Hondo Ohnaka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyCharacter Context triple: [Millennium Falcon: Smugglers Run, storyCharacter, Hondo Ohnaka]
-
A.
storyCharacterizedAs
Indicates that a story is described, portrayed, or defined as having a particular quality, style, or attribute.
-
B.
narrativeCharacter
chosen
Indicates that one entity functions as a character within the narrative or story associated with another entity.
-
C.
plotCharacter
Indicates a relationship where a character plays a role or participates in the narrative plot of a story or work.
-
D.
characters
Indicates that one entity is a character (or set of characters) associated with, appearing in, or belonging to another entity (such as a work, story, or medium).
-
E.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 5:42 p.m.