Triple
T20428329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apparition Test Centre |
E501061
|
entity |
| Predicate | examConsequenceOfFailure |
P140098
|
FINISHED |
| Object | denial of Apparition licence |
—
|
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: denial of Apparition licence | Statement: [Apparition Test Centre, examConsequenceOfFailure, denial of Apparition licence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examConsequenceOfFailure Context triple: [Apparition Test Centre, examConsequenceOfFailure, denial of Apparition licence]
-
A.
consequenceOfRevocation
Indicates that something occurs as a direct result of a prior revocation event or decision.
-
B.
consequenceOfApplication
Indicates that something occurs as a result or outcome of a particular application or use of something.
-
C.
consequenceOfCertification
Indicates that something occurs as a result of, or is caused by, a particular certification.
-
D.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
E.
violationConsequences
Indicates the negative outcomes, penalties, or repercussions that result from a violation of a rule, law, or agreement.
- 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_69e0b4aa68fc8190b1a14c55575ef04a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67baa91b881909dfd68ccca25063c |
completed | April 20, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:31 a.m.