Triple
T27284359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thanbyuzayat Township |
E688426
|
entity |
| Predicate | warCemetery |
P128172
|
FINISHED |
| Object | Thanbyuzayat War Cemetery |
—
|
NE NERFINISHED |
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: Thanbyuzayat War Cemetery | Statement: [Thanbyuzayat Township, warCemetery, Thanbyuzayat War Cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warCemetery Context triple: [Thanbyuzayat Township, warCemetery, Thanbyuzayat War Cemetery]
-
A.
countryOfCemetery
Indicates that a cemetery is located within the territory of a specified country.
-
B.
containsWarGravesOf
chosen
Indicates that a place or site includes burial locations or memorials for individuals who died in war.
-
C.
hasWarGravesMaintainedBy
Indicates that one entity contains war graves whose upkeep and preservation are carried out by another entity.
-
D.
associatedCemetery
Indicates that there is a relationship linking an entity (such as a person, event, or organization) to a specific cemetery with which it is connected.
-
E.
memorialSiteFor
Indicates that a place or structure serves as a dedicated site of remembrance or commemoration for a particular person, group, or event.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62753ec2481908aa814a112263356 |
completed | May 2, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:10 a.m.