Triple
T23945028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LUKE Arm |
E602889
|
entity |
| Predicate | fictionalReference |
P50141
|
FINISHED |
| Object | Star Wars franchise |
—
|
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 franchise | Statement: [LUKE Arm, fictionalReference, Star Wars franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalReference Context triple: [LUKE Arm, fictionalReference, Star Wars franchise]
-
A.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
-
B.
worksInFictionalContext
Indicates that an entity performs work or fulfills a role within a fictional or imagined setting rather than in real-world circumstances.
-
C.
fictionalFocus
Indicates that the primary emphasis or attention within a context is placed on fictional content, elements, or aspects.
-
D.
fictionalCharacter
chosen
Indicates that one entity is a fictional character that appears within the narrative world of another entity (such as a work, series, or franchise).
-
E.
createsInFiction
Indicates that one entity is the creator or originator of another entity within a fictional or narrative 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02dd0cc8190b32eb86bdfe0bf9a |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:11 p.m.