Triple
T7157004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exicure, Inc. |
E166837
|
entity |
| Predicate | aimsToTreat |
P75197
|
FINISHED |
| Object | cancer |
—
|
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: cancer | Statement: [Exicure, Inc., aimsToTreat, cancer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimsToTreat Context triple: [Exicure, Inc., aimsToTreat, cancer]
-
A.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
B.
aimsToMeasure
Indicates that one entity is intended or designed to quantify, assess, or evaluate another entity or property.
-
C.
aimsToProvide
Indicates that one entity intends or is designed to supply, deliver, or make available something to another entity.
-
D.
aimsToSolve
Indicates an intention or purpose directed toward resolving, addressing, or eliminating a particular problem, challenge, or issue.
-
E.
aimsToControl
Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
- F. None of above. chosen
Provenance (4 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e80f14808190907ee84523630d85 |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:47 p.m.