Triple
T25620902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GINA |
E642292
|
entity |
| Predicate | Title I regulates |
P171385
|
FINISHED |
| Object | group health plans |
—
|
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: group health plans | Statement: [GINA, Title I regulates, group health plans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Title I regulates Context triple: [GINA, Title I regulates, group health plans]
-
A.
regulatesTitle
Indicates that one entity has the authority or function to control, govern, or set rules regarding another entity’s official title.
-
B.
regulationName
Indicates the specific name or title assigned to a regulation that governs or constrains something.
-
C.
titleIIIName
Indicates that one entity is the official Title III–specific name or designation associated with another entity.
-
D.
regulationAtIssue
Indicates that a specific regulation is the subject of concern, dispute, or analysis in the given context.
-
E.
titleOfU.S.Code
Indicates that a specified title number or name corresponds to a particular section or portion of the United States Code.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 21, 2026, 5:04 p.m.