Triple
T21967888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warsaw Insurgents’ quarters |
E542505
|
entity |
| Predicate | locatedInCemeteryType |
P2742
|
FINISHED |
| Object | military cemetery |
—
|
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: military cemetery | Statement: [Warsaw Insurgents’ quarters, locatedInCemeteryType, military cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCemeteryType Context triple: [Warsaw Insurgents’ quarters, locatedInCemeteryType, military cemetery]
-
A.
locatedInCemetery
Indicates that one entity is situated within the grounds or area of a cemetery.
-
B.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
C.
cemeteryType
chosen
Indicates the specific kind or classification of a cemetery associated with an entity.
-
D.
locatedInTheAdministrativeTerritorialEntityOfBurial
Indicates that the place or site referenced is situated within the specified administrative territorial entity where the burial is located.
-
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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1245c5d148190af2a06190ba32feb |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8:02 p.m.