Triple
T5680233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qi |
E125181
|
entity |
| Predicate | imbalancesCause |
P694
|
FINISHED |
| Object | illness in traditional Chinese medicine |
—
|
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: illness in traditional Chinese medicine | Statement: [Qi, imbalancesCause, illness in traditional Chinese medicine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imbalancesCause Context triple: [Qi, imbalancesCause, illness in traditional Chinese medicine]
-
A.
causeOfIllness
Indicates that one entity is the reason or source responsible for another entity’s illness or disease.
-
B.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
primaryCauseCategory
Indicates the main type or classification of cause responsible for an outcome or event.
-
D.
deficiencyAssociatedWith
Indicates an association where a lack or insufficiency of one entity is related to the occurrence, presence, or severity of another entity.
-
E.
causeOfWeakness
Indicates that one entity is the reason or source that brings about the weakness 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.