Triple
T805771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Periscope |
E17428
|
entity |
| Predicate | hasUserInteraction |
P3970
|
FINISHED |
| Object | real-time chat |
—
|
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: real-time chat | Statement: [Periscope, hasUserInteraction, real-time chat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUserInteraction Context triple: [Periscope, hasUserInteraction, real-time chat]
-
A.
hasInteraction
chosen
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
B.
hasMouse
Indicates that an entity possesses, uses, or is associated with a mouse (typically a computer pointing device or a small rodent).
-
C.
hasInitial
Indicates that one entity possesses or is associated with the first letter or starting character of another entity’s name or value.
-
D.
hasPrimaryFocus
Indicates that something is the main subject, concern, or area of attention for an entity or activity.
-
E.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ace495348190aec66f35ea90bc89 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa70973c8190adbf08302d1103a9 |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.