Triple
T26175548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Behçet's disease |
E654529
|
entity |
| Predicate | stronglyAssociatedWith |
P2830
|
FINISHED |
| Object | HLA-B51 allele |
—
|
NE NERFINISHED |
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: HLA-B51 allele | Statement: [Behçet's disease, stronglyAssociatedWith, HLA-B51 allele]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stronglyAssociatedWith Context triple: [Behçet's disease, stronglyAssociatedWith, HLA-B51 allele]
-
A.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
B.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
C.
positionAssociatedWith
Indicates a relationship where a specific role, job, or position is linked or connected to a particular entity, context, or resource.
-
D.
associationWithHumans
Indicates a general relationship, connection, or involvement between an entity and one or more humans.
-
E.
originallyAssociatedWith
Indicates that an entity was first linked, connected, or affiliated with another entity before any later changes in association.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c6bc408819098c4288f77d75e38 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:37 p.m.