Triple
T25479362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill 60 Memorial |
E638520
|
entity |
| Predicate | nearbyMemorials |
P136177
|
FINISHED |
| Object | Caterpillar Crater |
—
|
NE NERFINISHED |
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: Caterpillar Crater | Statement: [Hill 60 Memorial, nearbyMemorials, Caterpillar Crater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyMemorials Context triple: [Hill 60 Memorial, nearbyMemorials, Caterpillar Crater]
-
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.
nearbyTomb
Indicates that one entity is located close to or in the immediate vicinity of a tomb.
-
D.
nearbyCemetery
Indicates that one entity is located close to or in the immediate vicinity of a cemetery.
-
E.
nearbyMonumentDedication
Indicates that a monument located close to a given reference point has been formally dedicated, typically in honor of a person, event, or concept.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 21, 2026, 2:30 p.m.