Triple
T36570570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer Cemetery (Fossil, Oregon) |
E902109
|
entity |
| Predicate | eraOfPrimaryBurials |
P68383
|
FINISHED |
| Object | 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: 19th century | Statement: [Pioneer Cemetery (Fossil, Oregon), eraOfPrimaryBurials, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfPrimaryBurials Context triple: [Pioneer Cemetery (Fossil, Oregon), eraOfPrimaryBurials, 19th century]
-
A.
eraOfMostBurials
Indicates the historical time period during which the greatest number of burials occurred for a given site or context.
-
B.
periodOfBurial
Indicates the time period or date range during which the burial of an entity took place.
-
C.
primaryDenominationOfBurials
Indicates the main religious denomination associated with the majority of burials at a given burial site or cemetery.
-
D.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
E.
timePeriodOfBurials
chosen
Indicates the span of time during which the burials associated with an entity took place.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.