Triple
T29302680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Courts of Justice of the Autonomous Communities |
E743002
|
entity |
| Predicate | notAbove |
P4503
|
FINISHED |
| Object | Supreme Court of Spain |
E370958
|
NE 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 of Spain | Statement: [High Courts of Justice of the Autonomous Communities, notAbove, Supreme Court of Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAbove Context triple: [High Courts of Justice of the Autonomous Communities, notAbove, Supreme Court of Spain]
-
A.
notAB
Indicates that the subject is explicitly not classified as type or category B.
-
B.
above
chosen
Indicates that one entity is positioned higher than another along a vertical axis, without implying direct contact.
-
C.
notWithin
Indicates that one entity is located outside the spatial or conceptual bounds of another entity.
-
D.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
-
E.
notAfter
Indicates that one event or entity does not occur later than (i.e., is earlier than or at the same time as) another in an ordering or timeline.
- F. None of above.
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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a0337c7389c8190b71d27b8eb8daf9a |
completed | May 12, 2026, 2:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a267e95815c81909caf78f41d98811e |
completed | June 8, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_6a0335b7b1588190b02a0ce6a08704aa |
completed | May 12, 2026, 2:14 p.m. |
Created at: April 28, 2026, 1:11 p.m.