Triple
T32631389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eve |
E834218
|
entity |
| Predicate | sharesTelepathicLinkWith |
P66148
|
FINISHED |
| Object | Patrick Ross |
—
|
NE NERFINISHED |
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: Patrick Ross | Statement: [Eve, sharesTelepathicLinkWith, Patrick Ross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesTelepathicLinkWith Context triple: [Eve, sharesTelepathicLinkWith, Patrick Ross]
-
A.
sharesTelepathicBondWith
chosen
Indicates a mutual telepathic connection through which two entities can directly share thoughts, feelings, or information.
-
B.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
C.
shareWith
Indicates that something is given, disclosed, or made accessible by one entity to another entity.
-
D.
sharesRouteWith
Indicates that two entities follow or operate along the same or overlapping route.
-
E.
sharesContextWith
Indicates that two entities occur within or are associated with the same situational, semantic, or environmental 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: May 1, 2026, 1:07 a.m.