Triple
T25784438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gonzales v. Carhart |
E649381
|
entity |
| Predicate | concernsMedicalProcedure |
P75671
|
FINISHED |
| Object | intact dilation and extraction (intact D&E) |
—
|
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: intact dilation and extraction (intact D&E) | Statement: [Gonzales v. Carhart, concernsMedicalProcedure, intact dilation and extraction (intact D&E)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsMedicalProcedure Context triple: [Gonzales v. Carhart, concernsMedicalProcedure, intact dilation and extraction (intact D&E)]
-
A.
concernsProcedure
chosen
Indicates that something is about, related to, or involves a particular procedure.
-
B.
concernsProblem
Indicates that something is about, related to, or deals with a particular problem or issue.
-
C.
isMedicallyRelevant
Indicates that something has significance, impact, or applicability within a medical or clinical context.
-
D.
hasHealthConcern
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
-
E.
concernsMeasure
Indicates that something is about or relates specifically to a particular quantitative measure or measurement.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 5:53 a.m.