Triple
T5160963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hodgkin lymphoma |
E116434
|
entity |
| Predicate | hasMajorType |
P62299
|
FINISHED |
| Object | classical Hodgkin lymphoma |
—
|
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: classical Hodgkin lymphoma | Statement: [Hodgkin lymphoma, hasMajorType, classical Hodgkin lymphoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorType Context triple: [Hodgkin lymphoma, hasMajorType, classical Hodgkin lymphoma]
-
A.
hasMajorCategory
Indicates that something is associated with or classified under a primary, overarching category.
-
B.
hasMajorComponent
Indicates that one entity includes another entity as a primary or most significant component or part.
-
C.
hasMajorRange
Indicates that one entity encompasses or defines the primary or most extensive range or scope associated with another entity.
-
D.
hasMajorBaseAmong
Indicates that one entity has its primary or most significant base of operations located within or among another entity or group.
-
E.
hasMajorTenantType
Indicates that an entity (such as a property or building) is associated with a primary or predominant type of tenant.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79bf9b088190a556dc02f10204e4 |
completed | March 20, 2026, 4:45 p.m. |
Created at: March 20, 2026, 1:44 p.m.