Triple
T22116064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hooggeregshof van Appèl |
E546544
|
entity |
| Predicate | highestFor |
P14338
|
FINISHED |
| Object | non-constitutional matters in South Africa |
—
|
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: non-constitutional matters in South Africa | Statement: [Hooggeregshof van Appèl, highestFor, non-constitutional matters in South Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestFor Context triple: [Hooggeregshof van Appèl, highestFor, non-constitutional matters in South Africa]
-
A.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
-
B.
highestPart
Indicates that one entity is the topmost or uppermost portion of another entity.
-
C.
formerHighest
Indicates that an entity once held the highest rank, position, or status in a given context but no longer does.
-
D.
highestOrgan
chosen
Indicates that one entity is the organ with the highest rank, level, or position within a specified system or hierarchy relative to another entity.
-
E.
highestRanking
Indicates that one entity holds the top or most senior rank relative to a set of other entities.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1294dc1148190b95ff00f475a6713 |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.