Triple
T16292313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studio 6A |
E395554
|
entity |
| Predicate | hasCallSignContext |
P29889
|
FINISHED |
| Object | NBC network production facility |
—
|
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: NBC network production facility | Statement: [Studio 6A, hasCallSignContext, NBC network production facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCallSignContext Context triple: [Studio 6A, hasCallSignContext, NBC network production facility]
-
A.
hasCallSignPrefix
Indicates that an entity’s call sign begins with a specified prefix.
-
B.
hasCallSignOwner
Indicates that a particular call sign is owned or assigned to a specific entity.
-
C.
supportsCallSign
Indicates that one entity is capable of recognizing, handling, or operating using a specified call sign.
-
D.
callSignScope
chosen
Indicates that a particular call sign is valid, applicable, or in effect only within a specified scope, context, or jurisdiction.
-
E.
hasCallsignCompanion
Indicates that one entity serves as a companion or associated partner to another entity’s callsign.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24919345881909ba4e7fe2e59340f |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.