Triple
T30260609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Gillard |
E769479
|
entity |
| Predicate | notableWorkFranchise |
P12396
|
FINISHED |
| Object | Star Wars |
E40213
|
NE 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: Star Wars | Statement: [Nick Gillard, notableWorkFranchise, Star Wars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkFranchise Context triple: [Nick Gillard, notableWorkFranchise, Star Wars]
-
A.
notableWorkInFranchise
chosen
Indicates that an entity has a significant or well-known work (such as a role, creation, or contribution) within a specific media franchise.
-
B.
notableSeriesFranchise
Indicates that an entity is a significant or well-known installment within a particular series or franchise.
-
C.
notableWorkSeries
Indicates that a work is part of a series for which the subject is notably known or recognized.
-
D.
notableWorkFeaturing
Indicates that a particular notable work (such as a book, film, or artwork) prominently includes, showcases, or is centered around a given entity.
-
E.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
- F. None of above.
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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27ac00ce808190ad34c19f7e588a09 |
completed | June 9, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:41 p.m.