Triple
T25703566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thalestris |
E644526
|
entity |
| Predicate | workExpandedEditionYear |
P16584
|
FINISHED |
| Object | 1714 |
—
|
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: 1714 | Statement: [Thalestris, workExpandedEditionYear, 1714]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workExpandedEditionYear Context triple: [Thalestris, workExpandedEditionYear, 1714]
-
A.
workExpandedEdition
Indicates that one work is an expanded edition of another, containing additional or revised material beyond the original.
-
B.
expandedEditionYear
chosen
Indicates the year in which a work’s expanded or enlarged edition was published or released.
-
C.
expansionReleaseYear
Indicates the year in which an expansion (such as an add-on, DLC, or extended version) is officially released.
-
D.
strengthenedEditionYear
Indicates the year in which a particular edition was revised or enhanced to become a strengthened version.
-
E.
expansionReleaseDate
Indicates the date on which an expansion (such as an add-on or supplementary release) is officially made available.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 8:59 p.m.