Triple
T3024890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippine Judicial Academy |
E82551
|
entity |
| Predicate | hasTrainingProgram |
P2489
|
FINISHED |
| Object | pre-judicature program |
—
|
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: pre-judicature program | Statement: [Philippine Judicial Academy, hasTrainingProgram, pre-judicature program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingProgram Context triple: [Philippine Judicial Academy, hasTrainingProgram, pre-judicature program]
-
A.
hasTrainingType
Indicates that an entity is associated with or characterized by a specific type or category of training.
-
B.
hasEducationalProgram
chosen
Indicates that an entity offers, runs, or is associated with a specific educational program.
-
C.
hasTrainingRole
Indicates that an entity holds or is assigned a specific role within a training or instructional context.
-
D.
hasTrained
Indicates that one entity has provided training or instruction to another entity.
-
E.
hasProgramme
Indicates that an entity is associated with or offers a particular programme (such as a course of study, plan, or structured set of activities).
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9abac0288190a30b42674eea501f |
completed | March 8, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.