Triple
T28978592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dota: Dragon’s Blood |
E734484
|
entity |
| Predicate | releaseDateBook3 |
P63663
|
FINISHED |
| Object | 2022-08-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: 2022-08-11 | Statement: [Dota: Dragon’s Blood, releaseDateBook3, 2022-08-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseDateBook3 Context triple: [Dota: Dragon’s Blood, releaseDateBook3, 2022-08-11]
-
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.
thirdEditionPublicationDate
chosen
Indicates the date on which the third edition of a work was published.
-
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.
releaseDatePartTwo
Indicates the date on which the second part or installment of something (e.g., a work, product, or event) is released.
-
E.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 28, 2026, 9:10 a.m.