Triple
T33837588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VOXI |
E867276
|
entity |
| Predicate | networkProvider |
P180471
|
FINISHED |
| Object | Vodafone UK |
—
|
NE NERFINISHED |
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: Vodafone UK | Statement: [VOXI, networkProvider, Vodafone UK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkProvider Context triple: [VOXI, networkProvider, Vodafone UK]
-
A.
networkService
Indicates that one entity provides or participates in a network-based service or functionality for another entity or system.
-
B.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
C.
networkFounded
Indicates that an organization or entity established or created a particular network.
-
D.
digitalProvider
Indicates that one entity serves as the supplier or source of digital services, content, or infrastructure for another entity.
-
E.
networkCode
Indicates that an entity is associated with, identified by, or operates under a specific network code within a communication or organizational network.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: May 1, 2026, 1:47 a.m.