Triple
T33235494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Soldier (plate) |
E850815
|
entity |
| Predicate | approximateDateOfDesign |
P49890
|
FINISHED |
| Object | c. 1523–1526 |
—
|
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: c. 1523–1526 | Statement: [The Soldier (plate), approximateDateOfDesign, c. 1523–1526]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDateOfDesign Context triple: [The Soldier (plate), approximateDateOfDesign, c. 1523–1526]
-
A.
approximateDesignYear
chosen
Indicates the estimated or inferred year in which something was designed, rather than a precisely known design year.
-
B.
approximateDepictionDate
Indicates the estimated or inferred date when a depiction was created, rather than a precise, confirmed date.
-
C.
designDate
Indicates the date on which something was originally designed or its design was completed.
-
D.
designedApproximately
Indicates that one entity was created, planned, or engineered to an estimated or imprecise degree in relation to another entity or specification.
-
E.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 1, 2026, 1:31 a.m.