Triple
T9894496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nubian Square |
E181534
|
entity |
| Predicate | renamingSupportedBy |
P91026
|
FINISHED |
| Object | local community activists |
—
|
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: local community activists | Statement: [Nubian Square, renamingSupportedBy, local community activists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamingSupportedBy Context triple: [Nubian Square, renamingSupportedBy, local community activists]
-
A.
renamingAnnouncedBy
Indicates that an entity’s change of name has been publicly announced or made known by another specified entity.
-
B.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
C.
officialRenaming
Indicates that an entity has been given a new official name, formally replacing its previous designation.
-
D.
renamedTo
Indicates that an entity has been given a new name, specifying the target name it was changed to.
-
E.
replacementName
Indicates that one entity serves as a substitute or successor name for another entity, effectively replacing the original designation.
- F. None of above. chosen
Provenance (4 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4a89e148190901753e67483d72c |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:39 p.m.