Triple
T9690329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Share Play |
E234519
|
entity |
| Predicate | guestCan |
P32554
|
FINISHED |
| Object | view host’s screen in real time |
—
|
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: view host’s screen in real time | Statement: [Share Play, guestCan, view host’s screen in real time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guestCan Context triple: [Share Play, guestCan, view host’s screen in real time]
-
A.
guestRole
Indicates that one entity participates in or is associated with another entity in the capacity of a guest, specifying the nature or type of that guest participation.
-
B.
guestFlow
Indicates the movement or progression of guests through a space, process, or experience over time.
-
C.
canVisit
chosen
Indicates that one entity is permitted or able to go to or access another entity or location.
-
D.
visitorStatus
Indicates the current state or condition of an entity in its role as a visitor (e.g., whether they are active, pending, past, or otherwise classified in their visit).
-
E.
supportsGuest
Indicates that one entity provides assistance, resources, or accommodation to another entity in the role of a guest.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d02b20881909d7c0d5d6aaafcb0 |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.