Triple
T27671184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HBO Go (U.S.) |
E697665
|
entity |
| Predicate | regionSpecificVersionOf |
P11942
|
FINISHED |
| Object | HBO Go |
—
|
NE NERFINISHED |
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: HBO Go | Statement: [HBO Go (U.S.), regionSpecificVersionOf, HBO Go]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionSpecificVersionOf Context triple: [HBO Go (U.S.), regionSpecificVersionOf, HBO Go]
-
A.
regionalVariantOf
chosen
Indicates that one entity is a version or form of another that is specific to a particular geographic region or locale.
-
B.
regionSpecificContent
Indicates that certain content is tailored, restricted, or applicable only to a particular geographic region or set of regions.
-
C.
regionSpecialization
Indicates that a region is designated or recognized as being particularly focused on, adapted to, or specialized in a specific function, activity, or domain.
-
D.
hasRegionalVariationsIn
Indicates that something exhibits different forms, versions, or characteristics depending on the geographic region.
-
E.
regionCompatibility
Indicates that two entities are suitable or allowed to coexist, operate, or interact within the same geographic or jurisdictional region.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 27, 2026, 2:41 p.m.