Triple
T27968501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Chinese Odyssey |
E704790
|
entity |
| Predicate | releaseDatePartOne |
P172366
|
FINISHED |
| Object | 1995-01-21 |
—
|
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: 1995-01-21 | Statement: [A Chinese Odyssey, releaseDatePartOne, 1995-01-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseDatePartOne Context triple: [A Chinese Odyssey, releaseDatePartOne, 1995-01-21]
-
A.
releasedAt
Indicates the time or date at which something (such as a product, work, or item) is made publicly available or officially launched.
-
B.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
C.
releasedUnder
Indicates that one entity is made available, distributed, or published according to the terms, conditions, or authority specified by another entity (such as a license, label, or governing framework).
-
D.
releasedDuring
Indicates that one entity was released within the time period defined by another entity.
-
E.
summaryReleaseDate
Indicates the date on which a summary is officially released or made publicly available.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 27, 2026, 7:36 p.m.