Triple
T31202253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thélus |
E795505
|
entity |
| Predicate | hasCommonwealthWarGraves |
P128172
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Thélus, hasCommonwealthWarGraves, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonwealthWarGraves Context triple: [Thélus, hasCommonwealthWarGraves, yes]
-
A.
hasWarGravesMaintainedBy
Indicates that one entity contains war graves whose upkeep and preservation are carried out by another entity.
-
B.
hasGraveOrMemorialOf
Indicates that a location or object serves as the grave or memorial site dedicated to a particular person or entity.
-
C.
hasCanadianWarCemeteryLocation
Indicates that a Canadian war cemetery is located at or associated with a specific place.
-
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.
containsWarGravesOf
chosen
Indicates that a place or site includes burial locations or memorials for individuals who died in war.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01d48f41f4819093a5b47288a073c1 |
completed | May 11, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_6a01d3fa278c8190838174dd96ef5dde |
completed | May 11, 2026, 1:04 p.m. |
Created at: April 29, 2026, 9:09 p.m.