Triple
T38490403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montgomery City Lines |
E918038
|
entity |
| Predicate | enforcedSegregationOnBuses |
P135760
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Montgomery City Lines, enforcedSegregationOnBuses, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcedSegregationOnBuses Context triple: [Montgomery City Lines, enforcedSegregationOnBuses, yes]
-
A.
stanceOnSegregation
Indicates a person or group’s expressed position, attitude, or viewpoint regarding racial or social segregation.
-
B.
desegregatedOn
Indicates the date or time at which previously segregated groups or facilities were officially integrated and segregation ended.
-
C.
raceSegregationStatus
chosen
Indicates whether entities are separated, treated differently, or organized based on racial categories or distinctions.
-
D.
desegregationEra
Indicates the time period during which segregation was being actively dismantled or ended in a given context.
-
E.
typeOfSegregationAddressed
Indicates the specific form or category of segregation that is being targeted, handled, or dealt with in a given 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.