Triple
T25643976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weary Dunlop memorial |
E642907
|
entity |
| Predicate | memorialForPerson |
P7860
|
FINISHED |
| Object | Sir Edward Weary Dunlop |
—
|
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: Sir Edward Weary Dunlop | Statement: [Weary Dunlop memorial, memorialForPerson, Sir Edward Weary Dunlop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memorialForPerson Context triple: [Weary Dunlop memorial, memorialForPerson, Sir Edward Weary Dunlop]
-
A.
memorialName
Indicates that a memorial is known by or designated with a particular name.
-
B.
commemoratedPerson
chosen
Indicates that the subject serves as a memorial or tribute to the referenced person.
-
C.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
D.
memorialSiteFor
Indicates that a place or structure serves as a dedicated site of remembrance or commemoration for a particular person, group, or event.
-
E.
commemoratesPersonDeath
Indicates that an event, object, or action serves to honor or mark the death of a specific person.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faa22e7c81908af7fe96952bebe0 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 5:48 p.m.