Triple
T4251382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vierville-sur-Mer |
E95859
|
entity |
| Predicate | hasCemeteryNearby |
P42242
|
FINISHED |
| Object | American military cemeteries in Normandy |
—
|
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: American military cemeteries in Normandy | Statement: [Vierville-sur-Mer, hasCemeteryNearby, American military cemeteries in Normandy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCemeteryNearby Context triple: [Vierville-sur-Mer, hasCemeteryNearby, American military cemeteries in Normandy]
-
A.
hasNearbyCemetery
chosen
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another entity.
-
B.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
C.
nearbyCemetery
Indicates that one entity is located close to or in the immediate vicinity of a cemetery.
-
D.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
E.
isPublicCemetery
Indicates that a cemetery is designated, maintained, or recognized as a public burial ground accessible for general community use.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ea059108190aa00f0f20673e0ac |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.