Triple
T7157011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exicure, Inc. |
E166837
|
entity |
| Predicate | SNAProperties |
P75198
|
FINISHED |
| Object | enhanced cellular uptake |
—
|
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: enhanced cellular uptake | Statement: [Exicure, Inc., SNAProperties, enhanced cellular uptake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SNAProperties Context triple: [Exicure, Inc., SNAProperties, enhanced cellular uptake]
-
A.
metaProperty
Indicates that one property functions as a higher-level descriptor or attribute about another property, rather than about an entity directly.
-
B.
eligibleProperties
Indicates that certain properties meet the required conditions or criteria to qualify for a specified purpose or status.
-
C.
spectralProperty
Indicates a relationship where an entity possesses or is characterized by a specific spectral feature, measurement, or behavior (e.g., in its frequency, wavelength, or energy spectrum).
-
D.
identifiesPropertyOf
Indicates that one entity specifies or denotes a particular property or attribute belonging to another entity.
-
E.
holeProperties
Indicates that certain attributes or characteristics are associated with a specific hole or void.
- 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.