Triple
T8561056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIA Special Courts |
E202690
|
entity |
| Predicate | canHoldTrialThroughVideoConferencing |
P83644
|
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, canHoldTrialThroughVideoConferencing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHoldTrialThroughVideoConferencing Context triple: [NIA Special Courts, canHoldTrialThroughVideoConferencing, true]
-
A.
canConfer
Indicates that one entity has the authority or ability to grant, bestow, or transfer a status, right, or benefit to another entity.
-
B.
canTry
Indicates that an entity has the possibility or permission to attempt performing a particular action or achieving a certain outcome.
-
C.
trialTypeHosted
Indicates that a particular trial was organized, conducted, or hosted by a specified entity.
-
D.
hasFirstTrial
Indicates that an entity is associated with its initial or earliest trial, test, or legal proceeding.
-
E.
openMeetingsRequirement
Indicates that certain meetings must be accessible to the public or non-participants, rather than being held in private or closed session.
- 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_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. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:20 p.m.