Triple
T1790586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invictus |
E39485
|
entity |
| Predicate | hasReleaseDate |
P21829
|
FINISHED |
| Object | 2009-12-11 |
—
|
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: 2009-12-11 | Statement: [Invictus, hasReleaseDate, 2009-12-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleaseDate Context triple: [Invictus, hasReleaseDate, 2009-12-11]
-
A.
hasPublicationDate
Indicates that an entity is associated with the specific date on which it was published.
-
B.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
C.
releasedDuring
Indicates that one entity was released within the time period defined by another entity.
-
D.
originallyReleasedOn
chosen
Indicates the date or platform on which something (such as a work, product, or media item) was first made publicly available.
-
E.
digitalReleaseDate
Indicates the date on which a work is first made available in digital form (e.g., online or as a digital file).
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab75457e54819096b8c6ae8c65550c |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61d165688190924962a98e07ff69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.