Triple
T13789138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBC Studios |
E331345
|
entity |
| Predicate | hasAudienceAccess |
P70174
|
FINISHED |
| Object | studio tours |
—
|
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: studio tours | Statement: [NBC Studios, hasAudienceAccess, studio tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudienceAccess Context triple: [NBC Studios, hasAudienceAccess, studio tours]
-
A.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
B.
audienceAccess
chosen
Indicates that one entity has permission or ability to access, view, or engage with a particular audience associated with another entity.
-
C.
hasAudiencePolicy
Indicates that there is a specified rule or policy governing which audience or group is allowed to access, view, or receive something.
-
D.
hasAudienceReach
Indicates the extent or scope of people or groups that are exposed to, can access, or are targeted by a particular entity, message, or activity.
-
E.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de024af32c8190a9bd1278e09564ba |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.