Triple
T38297410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sagrado |
E1032127
|
entity |
| Predicate | hasNearbyWarMemorial |
P136177
|
FINISHED |
| Object | World War I memorials |
—
|
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: World War I memorials | Statement: [Sagrado, hasNearbyWarMemorial, World War I memorials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyWarMemorial Context triple: [Sagrado, hasNearbyWarMemorial, World War I memorials]
-
A.
hasNearbyMemorials
chosen
Indicates that one or more memorials are located in close physical proximity to the referenced entity.
-
B.
commemoratesNearby
Indicates that one entity serves to honor or memorialize something located in close physical proximity to it.
-
C.
hasMemorialWall
Indicates that a place or entity includes or is associated with a wall dedicated to commemorating people, events, or memories.
-
D.
hasAdjacentMemorial
Indicates that one memorial is located directly next to or in close proximity to another memorial.
-
E.
memorialLocatedAt
Indicates that a memorial is situated or found at a specific location.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00c59b03dc8190870f0dd24603a1ef |
completed | May 10, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a00c5178bc88190b2a0e03f38314035 |
completed | May 10, 2026, 5:49 p.m. |
Created at: May 3, 2026, 4:30 p.m.