Triple
T142177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arlington National Cemetery |
E2876
|
entity |
| Predicate | burialEligibility |
P84
|
FINISHED |
| Object | members of the United States Armed Forces |
—
|
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: members of the United States Armed Forces | Statement: [Arlington National Cemetery, burialEligibility, members of the United States Armed Forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialEligibility Context triple: [Arlington National Cemetery, burialEligibility, members of the United States Armed Forces]
-
A.
eligibility
chosen
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
B.
canBeAwardedPosthumously
Indicates that something (such as an honor, title, or award) is eligible to be granted to a person after their death.
-
C.
countryOfBurial
Indicates the country in which a person or entity is buried.
-
D.
burialPlace
Indicates the location where a person or entity is buried.
-
E.
hasNotableBurials
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565559ac81909e0c4e095a7dfa27 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.