Triple
T14113371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court of appeal |
E339700
|
entity |
| Predicate | mayBeBelow |
P112867
|
FINISHED |
| Object | supreme court |
—
|
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: supreme court | Statement: [court of appeal, mayBeBelow, supreme court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeBelow Context triple: [court of appeal, mayBeBelow, supreme court]
-
A.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
-
B.
existsBelow
Indicates that at least one instance of an entity is located or occurs at a lower level or position relative to another entity.
-
C.
resultBelow
Indicates that one entity’s result, outcome, or measured value is lower than that of another entity.
-
D.
mayBeDowngradedTo
Indicates that one entity has the potential or permission to be reduced in status, level, or classification to another entity.
-
E.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600f992c81908133813f2894dcca |
completed | April 14, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.