Triple
T38490427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montgomery City Lines |
E918038
|
entity |
| Predicate | implementedDesegregation |
P190958
|
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, implementedDesegregation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedDesegregation Context triple: [Montgomery City Lines, implementedDesegregation, yes]
-
A.
typeOfSegregationAddressed
Indicates the specific form or category of segregation that is being targeted, handled, or dealt with in a given context.
-
B.
raceSegregationStatus
Indicates whether entities are separated, treated differently, or organized based on racial categories or distinctions.
-
C.
segregationBasis
Indicates the criterion or characteristic used as the basis for separating or distinguishing one group or set from another.
-
D.
massSegregation
Indicates that entities within a system are spatially distributed according to their mass, with more massive members preferentially concentrated toward the center.
-
E.
segregatedIn
Indicates that one entity is separated or isolated within a specific space, group, or context defined by another entity.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd34596288190b8e34a7a20b4c0db |
completed | May 7, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd31227708190a7df213597e66ca8 |
completed | May 7, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:31 p.m.