Triple
T36923482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klyntar |
E913270
|
entity |
| Predicate | bondingMethod |
P49770
|
FINISHED |
| Object | physical bonding with 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: physical bonding with host | Statement: [Klyntar, bondingMethod, physical bonding with host]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bondingMethod Context triple: [Klyntar, bondingMethod, physical bonding with host]
-
A.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
B.
hasBondType
chosen
Indicates the specific kind of bond or connection that exists between two related entities.
-
C.
typicalBonding
Indicates a usual or characteristic bonding relationship that commonly occurs between the involved entities.
-
D.
canBondWith
Indicates that one entity has the capability or compatibility to form a bond or connection with another entity.
-
E.
bindingQuality
Indicates the nature or degree of firmness, strength, or reliability with which one entity is bound, connected, or committed to another.
- 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_69f9fdcee55c8190ac5c514365310457 |
completed | May 5, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.