Triple
T20428315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apparition Test Centre |
E501061
|
entity |
| Predicate | examFocus |
P63100
|
FINISHED |
| Object | safety of Apparition |
—
|
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: safety of Apparition | Statement: [Apparition Test Centre, examFocus, safety of Apparition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examFocus Context triple: [Apparition Test Centre, examFocus, safety of Apparition]
-
A.
examContentArea
chosen
Indicates that an exam includes or focuses on a particular content area or subject domain.
-
B.
examType
Indicates the specific category or format of an exam associated with an assessment or testing event.
-
C.
entranceExam
Indicates that an entity is required to pass or participate in an entrance examination as a condition for admission or access to another entity.
-
D.
studiesFor
Indicates that one entity engages in studying or academic preparation with the purpose of achieving or supporting another entity (such as a goal, exam, or qualification).
-
E.
educationalFocus
Indicates the primary subject area or theme that an educational activity, program, or resource is centered on.
- 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.