Triple
T7485938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDF |
E176881
|
entity |
| Predicate | notableCaseArea |
P76513
|
FINISHED |
| Object | school desegregation |
—
|
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: school desegregation | Statement: [LDF, notableCaseArea, school desegregation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCaseArea Context triple: [LDF, notableCaseArea, school desegregation]
-
A.
notableAreaOfLaw
Indicates that a person or entity is particularly recognized or distinguished in a specific field or area of law.
-
B.
notableCourt
Indicates that a particular court is especially significant or noteworthy in relation to the subject.
-
C.
notableOperationArea
Indicates the geographic area or region where an entity primarily conducts or is recognized for its significant operations or activities.
-
D.
notableExceptionArea
Indicates that a specific area is recognized as an exception to a general rule, pattern, or classification that applies elsewhere.
-
E.
notableSupremeCourtCase
Indicates that a legal case is recognized as a significant or influential decision by the Supreme Court.
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f556955c8190bf014a065e04c5d8 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f105e320819091db3cdb1f1351f0 |
completed | March 27, 2026, 9:05 p.m. |
Created at: March 27, 2026, 3:42 p.m.