Triple
T16759799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic Act No. 1125 |
E407309
|
entity |
| Predicate | typeOfCourtCreated |
P8214
|
FINISHED |
| Object | specialized tax court |
—
|
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: specialized tax court | Statement: [Republic Act No. 1125, typeOfCourtCreated, specialized tax court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCourtCreated Context triple: [Republic Act No. 1125, typeOfCourtCreated, specialized tax court]
-
A.
typeOfJurisdictionCreated
Indicates that one entity establishes or defines the kind of legal or administrative jurisdiction associated with another entity.
-
B.
createdCourt
Indicates that an entity (typically a person or organization) established or founded a particular court.
-
C.
hasTypeOfCourt
chosen
Indicates that an entity is associated with or classified by a specific type or category of court.
-
D.
courtName
Indicates the official name assigned to a particular court within a legal or judicial system.
-
E.
createdLevelOfCourt
Indicates that an entity (such as a person, body, or law) is responsible for establishing or bringing into existence a particular level within a court system.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abeb3ab08190918f6bff686858be |
completed | April 18, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.