Triple
T17025457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office (2015 film) |
E413052
|
entity |
| Predicate | releaseDateInHongKong |
P125550
|
FINISHED |
| Object | 2015-09-24 |
—
|
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: 2015-09-24 | Statement: [Office (2015 film), releaseDateInHongKong, 2015-09-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseDateInHongKong Context triple: [Office (2015 film), releaseDateInHongKong, 2015-09-24]
-
A.
releaseDateChina
Indicates the date on which something (such as a product, work, or media) is officially released or made available in China.
-
B.
releaseDateTaiwan
Indicates the date on which something (such as a product, film, or media) was officially released in Taiwan.
-
C.
releaseDateAsia
Indicates the date on which something is officially released or made available in Asian markets.
-
D.
releaseDateSouthKorea
Indicates the date on which something (such as a product, film, or work) was officially released in South Korea.
-
E.
releaseDateUnitedKingdom
Indicates the date on which something (such as a product, work, or event) was officially released or made available in the United Kingdom.
- F. None of above. chosen
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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d46a5081908bc5681621dd8534 |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:33 a.m.