Triple
T8561064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIA Special Courts |
E202690
|
entity |
| Predicate | canTryConnectedOffences |
P67292
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NIA Special Courts, canTryConnectedOffences, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canTryConnectedOffences Context triple: [NIA Special Courts, canTryConnectedOffences, true]
-
A.
canTry
Indicates that an entity has the possibility or permission to attempt performing a particular action or achieving a certain outcome.
-
B.
includesAttemptedAndCompletedOffenses
Indicates that the relationship or count covers both offenses that were merely attempted and those that were fully completed.
-
C.
definesOffence
Indicates that one entity specifies or establishes the nature, elements, or scope of an offence associated with another entity.
-
D.
supportsMultipleOffensesPerIncident
chosen
Indicates that a single incident can be associated with, or give rise to, more than one distinct offense.
-
E.
isForConvictedOffenders
Indicates that something is intended to apply to, be used by, or be relevant for individuals who have been legally convicted of offenses.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe94af14481908b8762e0dc61f10f |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.