Triple
T26858346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battleground National Cemetery |
E676256
|
entity |
| Predicate | hasNumberOfGraves |
P14555
|
FINISHED |
| Object | less than 100 |
—
|
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: less than 100 | Statement: [Battleground National Cemetery, hasNumberOfGraves, less than 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfGraves Context triple: [Battleground National Cemetery, hasNumberOfGraves, less than 100]
-
A.
numberOfGravesApproximate
Indicates that the stated count of graves is an estimated or approximate number rather than an exact figure.
-
B.
numberOfBurials
chosen
Indicates the total count of burial events associated with a given entity.
-
C.
hasMassGraveOf
Indicates that a location or site contains a mass grave in which the referenced individuals or remains are buried.
-
D.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
E.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 27, 2026, 5:23 a.m.