Triple
T26581612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haymarket Square |
E667093
|
entity |
| Predicate | hasMemorialSculptureBy |
P75587
|
FINISHED |
| Object | Mary Brogger |
—
|
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: Mary Brogger | Statement: [Haymarket Square, hasMemorialSculptureBy, Mary Brogger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemorialSculptureBy Context triple: [Haymarket Square, hasMemorialSculptureBy, Mary Brogger]
-
A.
hasCommemorativeStructure
chosen
Indicates that one entity possesses or is associated with a physical structure created to honor, remember, or commemorate another entity or event.
-
B.
hasCommemorativePlaques
Indicates that one entity possesses or displays commemorative plaques associated with it.
-
C.
hasMemorialWall
Indicates that a place or entity includes or is associated with a wall dedicated to commemorating people, events, or memories.
-
D.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
E.
memorialWork
Indicates that one entity is a commemorative work (such as a monument, plaque, or artwork) created to honor or remember another 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 27, 2026, 2:03 a.m.