Triple
T34046664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restless legs syndrome |
E873102
|
entity |
| Predicate | hasAssociatedCondition |
P28410
|
FINISHED |
| Object | iron deficiency |
—
|
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: iron deficiency | Statement: [Restless legs syndrome, hasAssociatedCondition, iron deficiency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedCondition Context triple: [Restless legs syndrome, hasAssociatedCondition, iron deficiency]
-
A.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
B.
associatedWithCondition
chosen
Indicates that an entity has a relevant connection or linkage to a particular condition (such as a disease, state, or circumstance), without specifying the nature or strength of that connection.
-
C.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
-
D.
hasNumberOfConditions
Indicates that an entity is associated with a specific count of conditions it has or is subject to.
-
E.
hasChainCondition
Indicates that one entity is subject to, or satisfies, a specified chain condition imposed or characterized by 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 1, 2026, 1:51 a.m.