Triple
T37428670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albany Civil Rights Institute |
E930067
|
entity |
| Predicate | nearbyEventDocumented |
P156594
|
FINISHED |
| Object | Albany Movement mass meetings |
—
|
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: Albany Movement mass meetings | Statement: [Albany Civil Rights Institute, nearbyEventDocumented, Albany Movement mass meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyEventDocumented Context triple: [Albany Civil Rights Institute, nearbyEventDocumented, Albany Movement mass meetings]
-
A.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
-
B.
nearbyEventDate
Indicates that one event’s date occurs close in time to another event’s date.
-
C.
nearbyActivity
Indicates that an activity occurs close in space or proximity to a specified entity or location.
-
D.
hasNearbyHistoricalEvent
chosen
Indicates that a given entity is located close to the site where a specific historical event occurred.
-
E.
nearbyActivityHub
Indicates that one entity is located close enough to another entity that serves as a central hub or focal point for activities or events.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
Created at: May 3, 2026, 4:16 p.m.