Triple
T2358764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telegraph Avenue |
E47219
|
entity |
| Predicate | hasNotableEventHistory |
P18677
|
FINISHED |
| Object | People's Park protests vicinity |
—
|
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: People's Park protests vicinity | Statement: [Telegraph Avenue, hasNotableEventHistory, People's Park protests vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEventHistory Context triple: [Telegraph Avenue, hasNotableEventHistory, People's Park protests vicinity]
-
A.
hasNotableIncident
chosen
Indicates that an entity is associated with a significant or noteworthy event, occurrence, or incident.
-
B.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
C.
hasNotableCredit
Indicates that an entity is recognized for having a significant or noteworthy contribution, role, or acknowledgment associated with it.
-
D.
hasHistoryOf
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
E.
hasNotableDecision
Indicates that an entity is associated with a specific decision that is considered significant or noteworthy in some context.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc720b9048190a5d3b19e5e1f373a |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.