Triple
T30520948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | conduction aphasia |
E776691
|
entity |
| Predicate | hasPossibleCause |
P146054
|
FINISHED |
| Object | traumatic brain injury |
—
|
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: traumatic brain injury | Statement: [conduction aphasia, hasPossibleCause, traumatic brain injury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPossibleCause Context triple: [conduction aphasia, hasPossibleCause, traumatic brain injury]
-
A.
possibleCauseOf
chosen
Indicates that one entity is a potential, but not certain, cause or contributing factor to another entity or outcome.
-
B.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
C.
hasProposedCause
Indicates that one entity is suggested or hypothesized to be the cause or explanation for another entity or event.
-
D.
hasPossibleSymptom
Indicates that an entity (such as a condition or disease) may be associated with a particular symptom that can potentially occur.
-
E.
eligibleCause
Indicates that one entity qualifies as a valid or acceptable cause or reason for another entity or outcome.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: April 29, 2026, 8:17 p.m.