Triple
T8561055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIA Special Courts |
E202690
|
entity |
| Predicate | allowsProtectionOfWitnessIdentity |
P957
|
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, allowsProtectionOfWitnessIdentity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsProtectionOfWitnessIdentity Context triple: [NIA Special Courts, allowsProtectionOfWitnessIdentity, true]
-
A.
mayBeAffirmedRatherThanSworn
Indicates that a statement or testimony can be confirmed by affirmation instead of being given under a formal oath.
-
B.
witnesses
Indicates that one entity observes an event, action, or situation involving another entity, typically as a bystander or observer.
-
C.
protectedBy
chosen
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
D.
hasProtectionPurpose
Indicates that something is intended or designed to serve a protective function or goal.
-
E.
numberOfWitnessesHeard
Indicates the count of witnesses whose testimony or statements were heard in a given event or proceeding.
- 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.