Triple
T9938165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AET |
E194006
|
entity |
| Predicate | issuerNotableEvent |
P81564
|
FINISHED |
| Object | subject to U.S. Affordable Care Act market changes |
—
|
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: subject to U.S. Affordable Care Act market changes | Statement: [AET, issuerNotableEvent, subject to U.S. Affordable Care Act market changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerNotableEvent Context triple: [AET, issuerNotableEvent, subject to U.S. Affordable Care Act market changes]
-
A.
notableProtectiveIncident
Indicates that a significant event occurred in which one entity protected or defended another in a notable or remarkable way.
-
B.
notableIncidentType
Indicates the specific category or kind of significant event or incident associated with an entity.
-
C.
notableReport
Indicates that an entity has produced, authored, or is otherwise associated with a report that is considered notable or significant.
-
D.
investigatedEvent
Indicates that an event was the subject of an investigation or inquiry carried out by some agent.
-
E.
notableRegulatoryEvent
chosen
Indicates a significant regulatory action, decision, or change that has materially affected or is closely associated with the subject entity.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5e64760819094f599f158d32f33 |
completed | April 2, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:44 p.m.