Triple
T37617398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosa Parks Congressional Gold Medal Act |
E935961
|
entity |
| Predicate | honoreeNotableEvent |
P189515
|
FINISHED |
| Object | Montgomery Bus Boycott |
—
|
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: Montgomery Bus Boycott | Statement: [Rosa Parks Congressional Gold Medal Act, honoreeNotableEvent, Montgomery Bus Boycott]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoreeNotableEvent Context triple: [Rosa Parks Congressional Gold Medal Act, honoreeNotableEvent, Montgomery Bus Boycott]
-
A.
hasNotableHonoree
Indicates that an entity is notably dedicated to, named after, or honors a particular person or group.
-
B.
honoreeKnownFor
Indicates that an honoree is recognized or celebrated specifically for a particular work, achievement, contribution, or notable attribute.
-
C.
notablePersonAtEvent
Indicates that a particular person is notably associated with or recognized at a specific event.
-
D.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
E.
honorsPerson
Indicates that one entity formally recognizes, respects, or pays tribute to a specific person.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:18 p.m.