Triple
T35690750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ison system |
E1031281
|
entity |
| Predicate | hasInUniverseFranchise |
P102724
|
FINISHED |
| Object | Star Wars |
—
|
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 | Statement: [Ison system, hasInUniverseFranchise, Star Wars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInUniverseFranchise Context triple: [Ison system, hasInUniverseFranchise, Star Wars]
-
A.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
B.
hasFictionalUniverseStatus
Indicates that an entity holds a particular status or classification within a fictional universe or continuity.
-
C.
includedInFranchise
chosen
Indicates that an entity is part of, or belongs to, a larger franchise or franchise series.
-
D.
hasItemInFranchise
Indicates that an entity possesses or includes a specific item as part of a larger franchise or branded collection.
-
E.
hasFictionalUniverseProperty
Indicates that a fictional universe possesses a specific characteristic, attribute, or property.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0079e152648190a9da2add94fc1831 |
completed | May 10, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a0078f77f9c8190af357a6016a2bd53 |
completed | May 10, 2026, 12:24 p.m. |
Created at: May 3, 2026, 4:05 p.m.