Triple
T32472613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Courts |
E829885
|
entity |
| Predicate | decisionsCanBe |
P15229
|
FINISHED |
| Object | appealed to higher courts |
—
|
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: appealed to higher courts | Statement: [Family Courts, decisionsCanBe, appealed to higher courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionsCanBe Context triple: [Family Courts, decisionsCanBe, appealed to higher courts]
-
A.
decisionsAre
Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
-
B.
decisionsTakenBy
Indicates that one or more decisions are made or taken by a specified agent or entity.
-
C.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
D.
includesDecisionsBy
Indicates that something contains, encompasses, or takes into account decisions made by a specified party or set of parties.
-
E.
decisionsSubjectTo
chosen
Indicates that certain decisions are constrained by, dependent on, or must comply with specified conditions, approvals, or oversight.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 12:57 a.m.