Triple
T23651679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faces |
E584182
|
entity |
| Predicate | commercialReReleaseDate |
P36217
|
FINISHED |
| Object | 2021-10-15 |
—
|
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: 2021-10-15 | Statement: [Faces, commercialReReleaseDate, 2021-10-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialReReleaseDate Context triple: [Faces, commercialReReleaseDate, 2021-10-15]
-
A.
commercialReleaseYear
Indicates the calendar year in which a product, work, or item was first made commercially available to the public.
-
B.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
-
C.
reReleaseDate
chosen
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
D.
wideReleaseDate
Indicates the date on which a work (such as a film) is first made widely available to the general public across many locations or markets.
-
E.
businessReleaseDate
Indicates the date on which a product, service, or offering is officially made available for business or commercial use.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b358ce448190a654d2cd3e81ef83 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.