Triple
T28035341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariana |
E708388
|
entity |
| Predicate | approximateDateOfWork |
P877
|
FINISHED |
| Object | 1603–1604 |
—
|
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: 1603–1604 | Statement: [Mariana, approximateDateOfWork, 1603–1604]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDateOfWork Context triple: [Mariana, approximateDateOfWork, 1603–1604]
-
A.
associatedWorkDate
Indicates the date on which a related or associated work (such as a publication, performance, or creation) is linked to the subject entity.
-
B.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
approximateYearOfCompletion
Indicates the estimated calendar year in which something was completed, rather than an exact or confirmed year.
-
D.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
-
E.
approximateYearWritten
Indicates the estimated calendar year in which something was written, when the exact year is not known.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 27, 2026, 8:20 p.m.