Triple
T15212222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grytviken Cemetery |
E363541
|
entity |
| Predicate | burialCountApproximate |
P95901
|
FINISHED |
| Object | several dozen graves |
—
|
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: several dozen graves | Statement: [Grytviken Cemetery, burialCountApproximate, several dozen graves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialCountApproximate Context triple: [Grytviken Cemetery, burialCountApproximate, several dozen graves]
-
A.
numberOfBurials
Indicates the total count of burial events associated with a given entity.
-
B.
cemeteryBurialsSince
Indicates the number of burials that have occurred in a cemetery from a specified point in time onward.
-
C.
numberOfInterred
chosen
Indicates the total count of individuals who are buried or interred at a given site or within a specified context.
-
D.
burialsUntil
Indicates the number of burial events that remain or are scheduled to occur up to a specified point in time or condition.
-
E.
burialGroundCapacity
Indicates the maximum number of burials or remains that a burial ground is designed or allowed to accommodate.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0076c9e2481909d7a464b2172f4bf |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:11 a.m.