Triple
T4347348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Section 46, Arlington National Cemetery |
E97936
|
entity |
| Predicate | burialFor |
P25159
|
FINISHED |
| Object | U.S. military service members |
—
|
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: U.S. military service members | Statement: [Section 46, Arlington National Cemetery, burialFor, U.S. military service members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialFor Context triple: [Section 46, Arlington National Cemetery, burialFor, U.S. military service members]
-
A.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
B.
buriedFor
Indicates that one entity is buried on behalf of, in honor of, or as a memorial for another entity.
-
C.
burialText
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
-
D.
usedForBurialOf
chosen
Indicates that something serves or is employed as a means, place, or object for burying a particular entity.
-
E.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a5559c819081608b0aaf6a0e66 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.