Triple
T9830566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York v. Quarles |
E238770
|
entity |
| Predicate | publicSafetyExceptionCreated |
P90231
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [New York v. Quarles, publicSafetyExceptionCreated, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicSafetyExceptionCreated Context triple: [New York v. Quarles, publicSafetyExceptionCreated, yes]
-
A.
securityExceptionInvoked
Indicates that a security-related exception has been triggered or raised during execution.
-
B.
safetyFunction
Indicates that one entity serves as a safety-related function or mechanism that protects, safeguards, or reduces risk for another entity or process.
-
C.
safetyExpectation
Indicates an expected level or standard of safety that should be maintained or provided in a given context or relationship.
-
D.
notableSafety
Indicates that an entity is recognized for having significant safety characteristics, performance, or impact relative to others.
-
E.
observationSafety
Indicates that an observation or monitoring activity is conducted in a manner that ensures the safety of the subjects, observers, and environment involved.
- 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3297bd88190bf8c53a4ba00e0ae |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:32 p.m.