Triple
T2606438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State inspector general |
E58668
|
entity |
| Predicate | canReceive |
P28195
|
FINISHED |
| Object | complaints and allegations from the public |
—
|
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: complaints and allegations from the public | Statement: [New York State inspector general, canReceive, complaints and allegations from the public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canReceive Context triple: [New York State inspector general, canReceive, complaints and allegations from the public]
-
A.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
B.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
C.
canCollect
chosen
Indicates that one entity has the ability or permission to gather, receive, or take possession of another entity.
-
D.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
E.
canHandle
Indicates that an entity has the ability or capacity to manage, process, or deal with another entity or situation.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8def9bc8190b2e013abffc7b191 |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd80ab7248190ba06ba14fe4c5638 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:49 p.m.