Triple
T1112887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Lady Writing a Letter |
E11033
|
entity |
| Predicate | approximateInception |
P13193
|
FINISHED |
| Object | circa 1660s |
—
|
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: circa 1660s | Statement: [A Lady Writing a Letter, approximateInception, circa 1660s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateInception Context triple: [A Lady Writing a Letter, approximateInception, circa 1660s]
-
A.
inceptionTime
Indicates the specific point in time when an entity, event, or relationship begins or is first established.
-
B.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
C.
approximateYearOfCompletion
Indicates the estimated calendar year in which something was completed, rather than an exact or confirmed year.
-
D.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
E.
approximateStartYear
chosen
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.