Triple
T1903399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broca's aphasia |
E37743
|
entity |
| Predicate | possibleCause |
P10554
|
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: [Broca's aphasia, possibleCause, traumatic brain injury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleCause Context triple: [Broca's aphasia, possibleCause, traumatic brain injury]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
C.
causeSupported
Indicates that an entity provides backing, endorsement, or assistance to a particular cause or initiative.
-
D.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against another entity.
-
E.
debatedAsCauseOf
chosen
Indicates that one entity is discussed or argued over as a possible cause or origin 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.