Triple
T7193395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glossip v. Gross |
E167748
|
entity |
| Predicate | resultBelow |
P75673
|
FINISHED |
| Object | judgment of the Tenth Circuit affirmed |
—
|
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: judgment of the Tenth Circuit affirmed | Statement: [Glossip v. Gross, resultBelow, judgment of the Tenth Circuit affirmed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultBelow Context triple: [Glossip v. Gross, resultBelow, judgment of the Tenth Circuit affirmed]
-
A.
existsBelow
Indicates that at least one instance of an entity is located or occurs at a lower level or position relative to another entity.
-
B.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
-
C.
operatesBelow
Indicates that one entity functions, acts, or is positioned at a lower level, layer, or hierarchy relative to another entity.
-
D.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
E.
occursBelow
Indicates that one event or object takes place or is positioned at a lower level or beneath another in a spatial or hierarchical sense.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9036544819083c70a5d2135ba4b |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e8b5f6508190af28e06a7959d717 |
completed | March 27, 2026, 8:29 p.m. |
Created at: March 27, 2026, 2:50 p.m.