Triple
T7560177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Topa |
E178773
|
entity |
| Predicate | undergoesProcedure |
P53036
|
FINISHED |
| Object | surgery to restore female sex characteristics |
—
|
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: surgery to restore female sex characteristics | Statement: [Topa, undergoesProcedure, surgery to restore female sex characteristics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergoesProcedure Context triple: [Topa, undergoesProcedure, surgery to restore female sex characteristics]
-
A.
hadProcedure
chosen
Indicates that a subject underwent or received a specific medical or clinical procedure.
-
B.
hasSurgery
Indicates that a surgical procedure is performed on or undergone by an entity.
-
C.
underwent
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
-
D.
oftenUndergo
Indicates that an entity frequently experiences, is subjected to, or passes through a particular process, action, or change.
-
E.
undergoing
Indicates that an entity is currently experiencing, being subjected to, or in the process of a particular action, change, or treatment.
- 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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8dd96488190b4cca25ae8f7f95c |
completed | March 27, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:50 p.m.