Triple
T38490417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montgomery City Lines |
E918038
|
entity |
| Predicate | facedBoycottBy |
P11814
|
FINISHED |
| Object | African American community of Montgomery |
—
|
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: African American community of Montgomery | Statement: [Montgomery City Lines, facedBoycottBy, African American community of Montgomery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facedBoycottBy Context triple: [Montgomery City Lines, facedBoycottBy, African American community of Montgomery]
-
A.
boycottOccurredIn
Indicates that a boycott event took place within a specific location or geopolitical area.
-
B.
boycottLedBy
chosen
Indicates that a boycott is organized, initiated, or directed by a particular entity.
-
C.
boycottSupportedBy
Indicates that a boycott is endorsed, backed, or actively supported by a particular party or group.
-
D.
boycottType
Indicates the specific category or form of boycott involved in the relationship or action.
-
E.
reasonForBoycott
Indicates that one entity is the cause, motive, or justification for another entity’s decision to initiate or participate in a boycott.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.