Triple
T20428330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apparition Test Centre |
E501061
|
entity |
| Predicate | examConsequenceOfSuccess |
P79642
|
FINISHED |
| Object | granting 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: granting of Apparition licence | Statement: [Apparition Test Centre, examConsequenceOfSuccess, granting of Apparition licence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examConsequenceOfSuccess Context triple: [Apparition Test Centre, examConsequenceOfSuccess, granting of Apparition licence]
-
A.
consequenceOfCertification
chosen
Indicates that something occurs as a result of, or is caused by, a particular certification.
-
B.
consequenceOfApplication
Indicates that something occurs as a result or outcome of a particular application or use of something.
-
C.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
-
D.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
E.
significantEventConsequence
Indicates that one event leads to an important or impactful consequence for another event, state, or entity.
- 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_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. |
Created at: April 16, 2026, 11:31 a.m.