Triple
T27645999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BOCs |
E696713
|
entity |
| Predicate | laterServiceExpansion |
P54843
|
FINISHED |
| Object | wireless services |
—
|
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: wireless services | Statement: [BOCs, laterServiceExpansion, wireless services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterServiceExpansion Context triple: [BOCs, laterServiceExpansion, wireless services]
-
A.
laterExpansionCompletion
Indicates that the completion of an expansion occurs at a later time than another referenced event or expansion.
-
B.
sectorExpansion
Indicates an increase or broadening in the size, scope, or activity level of a particular sector or industry over time.
-
C.
laterExtendedIn
Indicates that an existing entity (such as a work, version, or specification) was subsequently expanded, updated, or built upon by a later entity.
-
D.
plannedExpansion
chosen
Indicates that an entity has a scheduled or intended increase in size, capacity, scope, or presence in the future.
-
E.
laterServiceRoute
Indicates that one service route occurs after or succeeds another service route in time.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 27, 2026, 2:29 p.m.