Triple
T181535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plessy v. Ferguson |
E3886
|
entity |
| Predicate | upheld |
P3106
|
FINISHED |
| Object | constitutionality of Jim Crow segregation laws |
—
|
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: constitutionality of Jim Crow segregation laws | Statement: [Plessy v. Ferguson, upheld, constitutionality of Jim Crow segregation laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upheld Context triple: [Plessy v. Ferguson, upheld, constitutionality of Jim Crow segregation laws]
-
A.
upheldBy
Indicates that one entity is supported, maintained, or validated by another, often through approval, enforcement, or confirmation of its validity.
-
B.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
-
C.
affirms
chosen
Indicates that one entity explicitly confirms, supports, or asserts the truth or validity of another entity, statement, or proposition.
-
D.
above
Indicates that one entity is positioned higher than another along a vertical axis, without implying direct contact.
-
E.
holding
Indicates that one entity is physically grasping, carrying, or keeping another entity in its possession or control.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25923507c8190bd7f6eda404b0da0 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566ccc288190add5624ede96d82b |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.