Triple
T30113807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSTM-TV |
E765356
|
entity |
| Predicate | hasLocalFocus |
P87246
|
FINISHED |
| Object | Syracuse community |
—
|
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: Syracuse community | Statement: [WSTM-TV, hasLocalFocus, Syracuse community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalFocus Context triple: [WSTM-TV, hasLocalFocus, Syracuse community]
-
A.
hasGlobalFocus
Indicates that something is oriented toward, concerned with, or applicable to worldwide or international scope rather than a local or regional one.
-
B.
hasLocationFocus
chosen
Indicates that the primary emphasis or relevance of something is centered on a specific location or place.
-
C.
hasCharacterFocus
Indicates that a work, scene, or segment centers primarily on a particular character’s experiences, perspective, or development.
-
D.
hasVisualFocus
Indicates that one entity is currently directing its visual attention or gaze toward another entity.
-
E.
hasActingFocus
Indicates that an entity is the primary performer or focal agent carrying out an action 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 29, 2026, 7:11 p.m.