Triple
T1080832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Court of Justiciary |
E23940
|
entity |
| Predicate | trialMode |
P23716
|
FINISHED |
| Object | jury trial |
—
|
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: jury trial | Statement: [High Court of Justiciary, trialMode, jury trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trialMode Context triple: [High Court of Justiciary, trialMode, jury trial]
-
A.
trial
Indicates that an entity is the subject of a legal or formal judicial proceeding to determine guilt, liability, or resolution of a dispute.
-
B.
testPilot
Indicates that an entity serves as a pilot responsible for testing and evaluating aircraft or related flight systems.
-
C.
offersTrialPeriod
Indicates that one entity provides another entity with a limited-time trial access to a product or service before full commitment or purchase.
-
D.
hasFirstTrial
Indicates that an entity is associated with its initial or earliest trial, test, or legal proceeding.
-
E.
triedBy
Indicates that an entity has made an attempt to perform an action on, or in relation to, another entity.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b946af788190b400644a2dec68c3 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73d9f08819093668104f129840e |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b80f0fb08190a19a50e38ae8f16c |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.