Triple
T1880813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taboo |
E39848
|
entity |
| Predicate | hasHealthHistory |
P4720
|
FINISHED |
| Object | testicular cancer survivor |
—
|
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: testicular cancer survivor | Statement: [Taboo, hasHealthHistory, testicular cancer survivor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHealthHistory Context triple: [Taboo, hasHealthHistory, testicular cancer survivor]
-
A.
hasHealthConcern
chosen
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
-
B.
hasPatient
Indicates that an action, event, or process involves a specific entity as the one undergoing or receiving its effects (the patient).
-
C.
hasResearchHistory
Indicates that an entity has a documented record of past research activities, projects, or studies.
-
D.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
E.
historicalContactWith
Indicates that two entities have interacted or been in communication with each other at some point in the past.
- 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb4f53f408190ae30e1a12721e7d7 |
completed | March 7, 2026, 5:17 a.m. |
| PD | Predicate disambiguation | batch_69abafe497a88190a1da6af2888b71b4 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.