Triple
T29952026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Savile |
E760793
|
entity |
| Predicate | creationDateApprox |
P13262
|
FINISHED |
| Object | late 19th 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: late 19th century | Statement: [Baron Savile, creationDateApprox, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creationDateApprox Context triple: [Baron Savile, creationDateApprox, late 19th century]
-
A.
estimatedYearOfCreation
chosen
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
B.
approximateDepictionDate
Indicates the estimated or inferred date when a depiction was created, rather than a precise, confirmed date.
-
C.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
approximateYearWritten
Indicates the estimated calendar year in which something was written, when the exact year is not known.
-
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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: April 29, 2026, 6:26 p.m.