Triple
T22693459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAF15 |
E561107
|
entity |
| Predicate | aggregationLinkedTo |
P68691
|
FINISHED |
| Object | neurodegeneration |
—
|
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: neurodegeneration | Statement: [TAF15, aggregationLinkedTo, neurodegeneration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggregationLinkedTo Context triple: [TAF15, aggregationLinkedTo, neurodegeneration]
-
A.
aggregationProperty
chosen
Indicates that one entity serves as an aggregation or summary of values or instances associated with another entity.
-
B.
compositionallyLinkedTo
Indicates that one entity is connected to another as part of a larger composition, such that changes or properties of one are meaningfully related to the combined whole.
-
C.
expansionLinkedTo
Indicates that one entity’s growth, increase, or enlargement is causally or logically connected to the expansion of another entity.
-
D.
commonlyLinkedTo
Indicates that one entity is frequently or typically associated, connected, or co-occurring with another entity.
-
E.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789c6ae481908975b7d27e7624ac |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.