Triple
T26643390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain Bell |
E668837
|
entity |
| Predicate | providedServiceBefore |
P69613
|
FINISHED |
| Object | divestiture of the Bell System |
—
|
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: divestiture of the Bell System | Statement: [Mountain Bell, providedServiceBefore, divestiture of the Bell System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedServiceBefore Context triple: [Mountain Bell, providedServiceBefore, divestiture of the Bell System]
-
A.
serviceBefore
chosen
Indicates that one service occurs, is provided, or is scheduled earlier in time than another service.
-
B.
previousServiceType
Indicates that one service type directly preceded another in a sequence or history of services.
-
C.
providesServices
Indicates that one entity supplies or performs services for the benefit or use of another entity.
-
D.
offeredService
Indicates that one entity has provided or made available a service to another entity.
-
E.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 27, 2026, 2:30 a.m.