Triple
T2924510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turing test |
E78810
|
entity |
| Predicate | interactionMedium |
P5765
|
FINISHED |
| Object | text-only communication |
—
|
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: text-only communication | Statement: [Turing test, interactionMedium, text-only communication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionMedium Context triple: [Turing test, interactionMedium, text-only communication]
-
A.
commonMedium
Indicates that two or more entities share the same medium or channel through which interaction, communication, or transmission occurs.
-
B.
socialMedia
Indicates a relationship where one entity uses, is associated with, or interacts through social networking or content-sharing platforms with another entity.
-
C.
mediaUse
Indicates that an entity makes use of, consumes, or engages with a particular medium or media resource.
-
D.
primaryMedium
chosen
Indicates the main material, format, or channel through which something is created, expressed, or communicated.
-
E.
mediaInfluence
Indicates that one entity affects, shapes, or alters another entity’s attitudes, behaviors, or perceptions through media content or channels.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.