Triple
T26745201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tel-el-Kebir |
E674377
|
entity |
| Predicate | hasCemeteryMaintainedBy |
P50501
|
FINISHED |
| Object | Commonwealth War Graves Commission |
—
|
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: Commonwealth War Graves Commission | Statement: [Tel-el-Kebir, hasCemeteryMaintainedBy, Commonwealth War Graves Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCemeteryMaintainedBy Context triple: [Tel-el-Kebir, hasCemeteryMaintainedBy, Commonwealth War Graves Commission]
-
A.
cemeteryMaintainedBy
chosen
Indicates that the upkeep, care, or management of a cemetery is performed or overseen by a specified agent or organization.
-
B.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
C.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
D.
cemeteryOwner
Indicates that one entity owns, controls, or holds legal responsibility for a cemetery associated with another entity.
-
E.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 3:51 a.m.