Triple
T16986513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic Act No. 9503 |
E412080
|
entity |
| Predicate | typeOfCourtAffected |
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. 9503, typeOfCourtAffected, specialized tax court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCourtAffected Context triple: [Republic Act No. 9503, typeOfCourtAffected, specialized tax court]
-
A.
affectedCourt
Indicates that a particular court is impacted or influenced by a specified action, decision, or legal matter.
-
B.
hasTypeOfCourt
chosen
Indicates that an entity is associated with or classified by a specific type or category of court.
-
C.
courtName
Indicates the official name assigned to a particular court within a legal or judicial system.
-
D.
decisionCourt
Indicates that a particular court rendered the decision or judgment in a given legal case or proceeding.
-
E.
typeOfJurisdiction
Indicates the specific kind or category of legal authority or control that one jurisdiction holds in relation to a given legal or administrative context.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d27b58908190a643bcbd105b1849 |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.