Triple
T14609643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Justice of the Land Court |
E342923
|
entity |
| Predicate | courtTypeOverseen |
P8214
|
FINISHED |
| Object | specialized trial 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 trial court | Statement: [Chief Justice of the Land Court, courtTypeOverseen, specialized trial court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtTypeOverseen Context triple: [Chief Justice of the Land Court, courtTypeOverseen, specialized trial court]
-
A.
overseenByCourt
Indicates that an action, process, or entity is subject to supervision, authority, or control by a court.
-
B.
hasTypeOfCourt
chosen
Indicates that an entity is associated with or classified by a specific type or category of court.
-
C.
courtCode
Indicates the specific court or judicial body associated with a legal case, proceeding, or record.
-
D.
courtStyle
Indicates the manner or stylistic approach in which a court conducts its proceedings or presents its decisions.
-
E.
courtBasedIn
Indicates that a particular court is located or headquartered in a specified place or jurisdiction.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb44f0dd48190a78662b5998a6722 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.