Triple
T28605521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roland Deschain's ka-tet |
E724034
|
entity |
| Predicate | bindingPrinciple |
P151219
|
FINISHED |
| Object | ka |
—
|
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: ka | Statement: [Roland Deschain's ka-tet, bindingPrinciple, ka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bindingPrinciple Context triple: [Roland Deschain's ka-tet, bindingPrinciple, ka]
-
A.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
B.
bindingFor
Indicates that one entity serves as the binding, constraint, or linkage mechanism that determines how another entity is associated, applied, or made effective.
-
C.
bindingAsTo
Indicates that one entity is legally or contractually binding upon another entity with respect to certain terms, obligations, or conditions.
-
D.
involvesPrinciple
chosen
Indicates that an action, process, or situation is based on, governed by, or makes essential use of a particular principle.
-
E.
boundIs
Indicates that one entity is constrained, limited, or obligated by another entity, condition, or rule.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:27 a.m.