Triple
T9407076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maison Pfister |
E226612
|
entity |
| Predicate | completionYearApproximate |
P22960
|
FINISHED |
| Object | mid-16th century |
—
|
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: mid-16th century | Statement: [Maison Pfister, completionYearApproximate, mid-16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completionYearApproximate Context triple: [Maison Pfister, completionYearApproximate, mid-16th century]
-
A.
approximateYearOfCompletion
chosen
Indicates the estimated calendar year in which something was completed, rather than an exact or confirmed year.
-
B.
endYearApprox
Indicates that the end year of an event, state, or relationship is known only approximately rather than as a precise calendar year.
-
C.
originalCompletionYear
Indicates the year in which something (such as a project, work, or construction) was first fully completed.
-
D.
workCompletionYear
Indicates the calendar year in which a particular work, project, or task was completed.
-
E.
releaseApproximateYear
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51c3fc988190ac34cc9e09f8ebfc |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:47 p.m.