Triple
T33775288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars: The Force Awakens (novelization) |
E865498
|
entity |
| Predicate | printPublicationDate |
P141501
|
FINISHED |
| Object | 2016-01-05 |
—
|
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: 2016-01-05 | Statement: [Star Wars: The Force Awakens (novelization), printPublicationDate, 2016-01-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: printPublicationDate Context triple: [Star Wars: The Force Awakens (novelization), printPublicationDate, 2016-01-05]
-
A.
hasPublicationDate
Indicates that an entity is associated with the specific date on which it was published.
-
B.
fullPublicationDate
chosen
Indicates the complete calendar date on which something is formally published, including day, month, and year.
-
C.
finalPublicationDate
Indicates the date on which a work is officially and definitively published in its final form.
-
D.
alternativePublicationDate
Indicates that an entity has another valid or related publication date different from its primary or original publication date.
-
E.
OJPublicationDate
Indicates the date on which something is officially published in the Official Journal.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.