Triple
T3024715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Trial Courts of the Philippines |
E82547
|
entity |
| Predicate | hasBranchType |
P1988
|
FINISHED |
| Object | regular Regional Trial Court branch |
—
|
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: regular Regional Trial Court branch | Statement: [Regional Trial Courts of the Philippines, hasBranchType, regular Regional Trial Court branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchType Context triple: [Regional Trial Courts of the Philippines, hasBranchType, regular Regional Trial Court branch]
-
A.
branchType
chosen
Indicates the specific kind or category of branch that an entity belongs to or is associated with.
-
B.
isPartOfBranchTypically
Indicates that something is typically a component or subdivision within a larger branch.
-
C.
hasMajorBranch
Indicates that one entity possesses or includes another entity as a primary or principal subdivision or branch.
-
D.
isUniqueBranchOf
Indicates that one branch is the sole or distinct sub-branch associated with a particular parent entity or structure.
-
E.
hasTrailType
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
- 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.