Triple
T36923489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klyntar |
E913270
|
entity |
| Predicate | bondingRisk |
P136373
|
FINISHED |
| Object | can exert corrupting influence on host |
—
|
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: can exert corrupting influence on host | Statement: [Klyntar, bondingRisk, can exert corrupting influence on host]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bondingRisk Context triple: [Klyntar, bondingRisk, can exert corrupting influence on host]
-
A.
riskBasis
Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
-
B.
hasRiskFrom
chosen
Indicates that one entity is exposed to or may suffer potential harm, loss, or adverse effects as a result of another entity.
-
C.
bondingEffect
Indicates the extent to which one entity’s presence, action, or interaction strengthens or enhances the bond or attachment between entities.
-
D.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
E.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.