Triple
T17181858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graves disease |
E417002
|
entity |
| Predicate | hasOcularManifestation |
P62906
|
FINISHED |
| Object | exophthalmos |
—
|
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: exophthalmos | Statement: [Graves disease, hasOcularManifestation, exophthalmos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOcularManifestation Context triple: [Graves disease, hasOcularManifestation, exophthalmos]
-
A.
eyeCondition
Indicates that an entity has, experiences, or is characterized by a particular condition or disorder affecting the eyes.
-
B.
coma
Indicates that an entity is in a state of prolonged unconsciousness and unresponsiveness, typically due to severe injury or illness.
-
C.
hasEyes
Indicates that an entity possesses eyes as physical features.
-
D.
eyeAssociation
Indicates a relationship where one entity is associated with, linked to, or characterized by a particular eye or eye-related feature of another entity.
-
E.
manifestationsInclude
chosen
Indicates that one entity’s manifestations or concrete expressions contain or encompass those of another entity.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc1187808190aeaa0d0e6487957e |
completed | April 18, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.