Triple
T12763138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Optimum Online |
E305044
|
entity |
| Predicate | serviceAreaFocus |
P104835
|
FINISHED |
| Object | regional ISP in the northeastern U.S. |
—
|
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: regional ISP in the northeastern U.S. | Statement: [Optimum Online, serviceAreaFocus, regional ISP in the northeastern U.S.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceAreaFocus Context triple: [Optimum Online, serviceAreaFocus, regional ISP in the northeastern U.S.]
-
A.
serviceAreaName
Indicates the designated name of the geographic or functional area that a service covers or operates within.
-
B.
areaOfService
chosen
Indicates the geographic or functional region within which a service is provided or applicable.
-
C.
branchOfServiceFocus
Indicates that one entity is the primary military or organizational branch of service emphasized, specialized in, or targeted by another entity or activity.
-
D.
areaServed
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
E.
serviceAreaCharacteristic
Indicates a relationship where a service area is associated with a specific attribute or feature that characterizes it.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8f9f588190bffdea878856204b |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.