Triple
T18223642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24/7 (HBO Sports documentary series) |
E436368
|
entity |
| Predicate | cameraAccess |
P6894
|
FINISHED |
| Object | locker rooms |
—
|
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: locker rooms | Statement: [24/7 (HBO Sports documentary series), cameraAccess, locker rooms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameraAccess Context triple: [24/7 (HBO Sports documentary series), cameraAccess, locker rooms]
-
A.
mediaAccess
chosen
Indicates that one entity has the ability, permission, or means to view, use, or interact with a particular media resource.
-
B.
frontCameraFeature
Indicates that an entity has a specified feature, capability, or characteristic associated with its front-facing camera.
-
C.
supportsCameraControl
Indicates that one entity provides functionality for another entity to remotely manage or adjust camera settings or operations.
-
D.
hasCamera
Indicates that an entity is equipped with or possesses a camera.
-
E.
cameraConfiguration
Indicates the specific setup or arrangement of a camera’s parameters or components in a given context.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e47d9b348190897d5a1e70b39ec5 |
completed | April 19, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.