Triple
T19593710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prairie Band Potawatomi Nation Tribal Court |
E470298
|
entity |
| Predicate | mayHaveBranch |
P136390
|
FINISHED |
| Object | appellate 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: appellate court | Statement: [Prairie Band Potawatomi Nation Tribal Court, mayHaveBranch, appellate court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHaveBranch Context triple: [Prairie Band Potawatomi Nation Tribal Court, mayHaveBranch, appellate court]
-
A.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
B.
possibleBranch
Indicates that one entity can serve as an alternative or potential continuation path branching from another entity.
-
C.
hadBranchIn
Indicates that an organization or entity maintained a branch, office, or subsidiary located in another specified place or entity.
-
D.
hasBranchOffice
Indicates that one organization maintains a branch office or subsidiary location in another place or entity.
-
E.
branchesFrom
Indicates that one entity originates or diverges from another as a subordinate or offshoot path, structure, or lineage.
- F. None of above. chosen
Provenance (4 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640782e2c8190b5baef07a2bdd015 |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:43 p.m.