Triple
T19177780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overmind |
E469482
|
entity |
| Predicate | mediumOfContact |
P2798
|
FINISHED |
| Object | non-physical psychic plane |
—
|
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: non-physical psychic plane | Statement: [Overmind, mediumOfContact, non-physical psychic plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediumOfContact Context triple: [Overmind, mediumOfContact, non-physical psychic plane]
-
A.
commonMedium
Indicates that two or more entities share the same medium or channel through which interaction, communication, or transmission occurs.
-
B.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
-
C.
mediumOfCommunicationFor
Indicates that one entity serves as the medium or channel through which another entity communicates or conveys information.
-
D.
earlyContact
Indicates that one entity initiates contact with another earlier than a typical, expected, or reference time.
-
E.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f618f18c8190b98995fda4b6fea0 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.