Triple
T9690332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Share Play |
E234519
|
entity |
| Predicate | hostMust |
P11374
|
FINISHED |
| Object | own the game being shared |
—
|
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: own the game being shared | Statement: [Share Play, hostMust, own the game being shared]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostMust Context triple: [Share Play, hostMust, own the game being shared]
-
A.
hostRequirement
chosen
Indicates that one entity specifies or imposes necessary conditions or resources that another entity (the host) must provide or satisfy.
-
B.
host
Indicates that one entity provides space, resources, or services to accommodate, receive, or entertain another entity.
-
C.
hostStar
Indicates that one celestial object serves as the primary star around which another object, such as a planet or system, is associated or orbits.
-
D.
hostsPartOf
Indicates that one entity serves as the hosting environment or container for a specific part or component of another entity.
-
E.
hostRock
Indicates that one rock body serves as the surrounding or enclosing rock in which another geological feature (such as an ore deposit, vein, or intrusion) occurs.
- 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.