Triple
T38137399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Soldiers’ Monument |
E952387
|
entity |
| Predicate | positionInCemetery |
P3802
|
FINISHED |
| Object | central feature |
—
|
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: central feature | Statement: [Central Soldiers’ Monument, positionInCemetery, central feature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInCemetery Context triple: [Central Soldiers’ Monument, positionInCemetery, central feature]
-
A.
locatedInCemetery
chosen
Indicates that one entity is situated within the grounds or area of a cemetery.
-
B.
burialCoordinates
Indicates the geographic location where an entity is buried, typically expressed as spatial coordinates.
-
C.
burialPlace
Indicates the location where a person or entity is buried.
-
D.
locatedInTheAdministrativeTerritorialEntityOfBurial
Indicates that the place or site referenced is situated within the specified administrative territorial entity where the burial is located.
-
E.
tombLocatedIn
Indicates that a particular tomb is situated within or at a specified location or place.
- 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0017dd31d08190aa5e9f72df83733a |
completed | May 10, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_6a0015a1deb88190b9cdaa60455b0a33 |
completed | May 10, 2026, 5:20 a.m. |
Created at: May 3, 2026, 4:21 p.m.