Triple
T6929490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the color line |
E160395
|
entity |
| Predicate | persistsIn |
P11419
|
FINISHED |
| Object | mass incarceration disparities |
—
|
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: mass incarceration disparities | Statement: [the color line, persistsIn, mass incarceration disparities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: persistsIn Context triple: [the color line, persistsIn, mass incarceration disparities]
-
A.
persistsAfter
Indicates that one state, condition, or effect continues to exist after a specified event, time point, or other state has occurred or ended.
-
B.
persistence
chosen
Indicates a continued or repeated existence, occurrence, or effort of something over time despite potential changes or obstacles.
-
C.
permanence
Indicates that a state, condition, or relationship continues to hold over time without significant change or interruption.
-
D.
supportsPersistence
Indicates that one entity enables or provides the capability for another entity’s data or state to be stored and retained over time.
-
E.
keptIn
Indicates that one entity is stored, contained, or maintained inside another entity as its location or container.
- 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da1f5fcc8190b43f53f90fc1821c |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:27 p.m.