Triple
T15368419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Your Eyes |
E367474
|
entity |
| Predicate | telepathicLinkDepicted |
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: [In Your Eyes, telepathicLinkDepicted, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telepathicLinkDepicted Context triple: [In Your Eyes, telepathicLinkDepicted, 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.
spiritualConnectionTo
Indicates a non-physical, often transcendent or faith-based bond or relationship that exists between two entities.
-
D.
linkedFigure
Indicates that one figure is associated or connected to another figure, typically as a reference or related visual element.
-
E.
associatedMystic
Indicates a relationship where one entity is linked or connected to another through a mystical, spiritual, or esoteric association.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e4a7cdc8190b7b48c97e774c306 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca9ab7e88190a9261ef27be665b1 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.