Triple
T37985842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myall Creek massacre |
E947684
|
entity |
| Predicate | commemorativePath |
P500
|
FINISHED |
| Object | Myall Creek Memorial Walk |
—
|
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: Myall Creek Memorial Walk | Statement: [Myall Creek massacre, commemorativePath, Myall Creek Memorial Walk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commemorativePath Context triple: [Myall Creek massacre, commemorativePath, Myall Creek Memorial Walk]
-
A.
commemoratedBy
chosen
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
B.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
-
C.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
D.
commemoratesField
Indicates that one entity serves to honor, remember, or mark the significance of another entity, event, or achievement.
-
E.
commemoratesCity
Indicates that something serves as a memorial or tribute specifically to a particular city.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:20 p.m.