Triple
T20942036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resurrection |
E515746
|
entity |
| Predicate | releaseYearApproximation |
P49730
|
FINISHED |
| Object | circa 1968 |
—
|
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 1968 | Statement: [Resurrection, releaseYearApproximation, circa 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseYearApproximation Context triple: [Resurrection, releaseYearApproximation, circa 1968]
-
A.
releaseApproximateYear
chosen
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
B.
retitleApproxYear
Indicates that an entity was retitled or renamed around an approximate year, rather than at a precisely known date.
-
C.
approximateYearWritten
Indicates the estimated calendar year in which something was written, when the exact year is not known.
-
D.
approximatePremiereYear
Indicates the estimated calendar year in which something, typically a work or event, first premiered.
-
E.
discoveryYear_approx
Indicates that the year associated with a discovery is known only approximately rather than as an exact calendar 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f9571c448190b314a66e02772b1e |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:50 p.m.