Triple
T28507969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PWK |
E721407
|
entity |
| Predicate | examRelationship |
P164600
|
FINISHED |
| Object | recommended preparation for OSCP exam |
—
|
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: recommended preparation for OSCP exam | Statement: [PWK, examRelationship, recommended preparation for OSCP exam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examRelationship Context triple: [PWK, examRelationship, recommended preparation for OSCP exam]
-
A.
atGradeRelation
Indicates that one entity is positioned at the same grade or elevation level as another entity.
-
B.
relationshipToStudents
Indicates the type or nature of connection one entity has with students, such as role, affiliation, or responsibility toward them.
-
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.
examCategory
Indicates the classification or type of an exam within a defined set of exam categories.
-
E.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f72cc848190bfb909c595cabefd |
completed | May 2, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 3:10 a.m.