Triple
T38188872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier Communications |
E1005395
|
entity |
| Predicate | focusStrategy |
P194404
|
FINISHED |
| Object | expansion of fiber broadband |
—
|
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: expansion of fiber broadband | Statement: [Frontier Communications, focusStrategy, expansion of fiber broadband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusStrategy Context triple: [Frontier Communications, focusStrategy, expansion of fiber broadband]
-
A.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
B.
focusModel
Indicates that one entity serves as the primary or central model that another entity is directed toward, based on, or concentrated on.
-
C.
focusOf
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
-
D.
focusShift
Indicates a change in attention or emphasis from one entity or topic to another.
-
E.
focusTrait
Indicates that one entity is characterized by, or primarily associated with, a particular trait or attribute of another entity.
- F. None of above. chosen
Provenance (4 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: May 3, 2026, 4:29 p.m.