Triple
T16618173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Merri-bek |
E403748
|
entity |
| Predicate | renamingProcess |
P30638
|
FINISHED |
| Object | community consultation |
—
|
LITERAL FINISHED |
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: community consultation | Statement: [City of Merri-bek, renamingProcess, community consultation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamingProcess Context triple: [City of Merri-bek, renamingProcess, community consultation]
-
A.
replacedProcess
Indicates that one process has been substituted or superseded by another process.
-
B.
contextOfRenaming
chosen
Indicates the situational or historical context in which an entity’s name was or is being changed.
-
C.
renamingAnnouncedBy
Indicates that an entity’s change of name has been publicly announced or made known by another specified entity.
-
D.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
E.
renamingSupportedBy
Indicates that one entity provides the capability or functionality to perform renaming operations on 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754bc4cc8190a586732fc6507b40 |
completed | April 18, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.