Triple
T32783620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ypres Reservoir Cemetery |
E838424
|
entity |
| Predicate | hasRegisterLocation |
P204045
|
FINISHED |
| Object | cemetery entrance shelter |
—
|
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: cemetery entrance shelter | Statement: [Ypres Reservoir Cemetery, hasRegisterLocation, cemetery entrance shelter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegisterLocation Context triple: [Ypres Reservoir Cemetery, hasRegisterLocation, cemetery entrance shelter]
-
A.
identifiesRegistrationLocation
Indicates that an entity specifies the place or jurisdiction where a registration is or should be recorded.
-
B.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
C.
hasStageLocation
Indicates that an event, process, or staged activity occurs at or is associated with a specific location.
-
D.
hasActLocation
Indicates that an action or event occurs at, or is associated with, a specific location.
-
E.
hasProgramLocation
Indicates that a program, event, or activity takes place at or is associated with a specific location.
- F. None of above. chosen
Provenance (4 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0311c202408190be88a85337aacf11 |
completed | May 12, 2026, 11:40 a.m. |
| PD | Predicate disambiguation | batch_6a0310b0c9c88190ab218d47d4f432ed |
completed | May 12, 2026, 11:36 a.m. |
| PDg | Predicate description generation | batch_6a0311c145a08190ba7658db898ab7d6 |
completed | May 12, 2026, 11:40 a.m. |
Created at: May 1, 2026, 1:14 a.m.