Triple
T14799078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aberdeen Division |
E347856
|
entity |
| Predicate | judicialBodyType |
P3734
|
FINISHED |
| Object | trial court division |
—
|
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: trial court division | Statement: [Aberdeen Division, judicialBodyType, trial court division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judicialBodyType Context triple: [Aberdeen Division, judicialBodyType, trial court division]
-
A.
judicialBody
Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
-
B.
typeOfJurisdictionBody
Indicates that one entity functions as the jurisdictional authority or governing body for the other entity.
-
C.
judicialBodyName
Indicates the official name or title by which a judicial body (such as a court or tribunal) is designated.
-
D.
typeOfClericalBody
Indicates that one entity is a specific kind or category of clerical or religious governing body in relation to another.
-
E.
typeOfJurisdiction
chosen
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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd6131f08190885f1d27b4bfac7a |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.