Triple
T18349400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippine Bar |
E439624
|
entity |
| Predicate | examSubjectsInclude |
P63100
|
FINISHED |
| Object | Political Law |
—
|
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: Political Law | Statement: [Philippine Bar, examSubjectsInclude, Political Law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examSubjectsInclude Context triple: [Philippine Bar, examSubjectsInclude, Political Law]
-
A.
writtenExamSubjectsInclude
Indicates that the set of subjects specified is included among the subjects covered by a particular written exam.
-
B.
examType
Indicates the specific category or format of an exam associated with an assessment or testing event.
-
C.
examPatternIncludes
Indicates that a particular exam pattern contains or encompasses a specified component, section, or element as part of its structure.
-
D.
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.
-
E.
examContentArea
chosen
Indicates that an exam includes or focuses on a particular content area or subject domain.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e514f66a4c8190a0ba53d3b349178a |
completed | April 19, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.