Triple
T4370950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lone Pine Cemetery |
E98893
|
entity |
| Predicate | numberOfUnidentifiedBurials |
P55820
|
FINISHED |
| Object | over 600 |
—
|
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: over 600 | Statement: [Lone Pine Cemetery, numberOfUnidentifiedBurials, over 600]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfUnidentifiedBurials Context triple: [Lone Pine Cemetery, numberOfUnidentifiedBurials, over 600]
-
A.
numberOfBurials
Indicates the total count of burial events associated with a given entity.
-
B.
numberOfMassGraves
Indicates the quantity of mass graves associated with or present at a given entity or location.
-
C.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
D.
hasNotableBurials
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
-
E.
finalDispositionOfRemains
Indicates the relationship specifying how a person's physical remains are ultimately handled, treated, or placed after death.
- F. None of above. chosen
Provenance (4 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3521cb7ec8190b7b79675871d97d8 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:17 p.m.