Triple
T12901309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuvok |
E308617
|
entity |
| Predicate | telepathicAbility |
P65440
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tuvok, telepathicAbility, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telepathicAbility Context triple: [Tuvok, telepathicAbility, yes]
-
A.
sharesTelepathicBondWith
Indicates a mutual telepathic connection through which two entities can directly share thoughts, feelings, or information.
-
B.
featuresTelepathy
chosen
Indicates that an entity possesses or involves the ability to communicate or perceive thoughts directly mind-to-mind without conventional sensory interaction.
-
C.
forceAbility
Indicates that one entity has the power or capacity to compel, influence, or cause another entity to act or change in a particular way.
-
D.
spokenIncantation
Indicates that an entity has uttered a specific magical or ritual phrase, typically to invoke an effect or power.
-
E.
patronusAbility
Indicates the ability of an entity to produce or use a Patronus (a protective magical manifestation) in relation to another entity or context.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97180ee708190b60a3e58c42f764f |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.