Triple
T25530555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annmary Brown Memorial |
E639898
|
entity |
| Predicate | hasMemorialRoleFor |
P89478
|
FINISHED |
| Object | Annmary Brown |
—
|
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: Annmary Brown | Statement: [Annmary Brown Memorial, hasMemorialRoleFor, Annmary Brown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemorialRoleFor Context triple: [Annmary Brown Memorial, hasMemorialRoleFor, Annmary Brown]
-
A.
memorialRole
chosen
Indicates that an entity holds a specific role, capacity, or function in relation to a memorial or commemorative context.
-
B.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
C.
commemoratesRoleAs
Indicates that something serves to honor or recognize a specific role or position held by an entity.
-
D.
hasMemorialContext
Indicates that something is related to, associated with, or situated within the context of a memorial or commemorative setting.
-
E.
hasGraveOrMemorialOf
Indicates that a location or object serves as the grave or memorial site dedicated to a particular person or entity.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 21, 2026, 3:14 p.m.