Triple
T15203091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BT Mobile |
E363314
|
entity |
| Predicate | billingRelationship |
P91060
|
FINISHED |
| Object | BT Group billing systems |
—
|
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: BT Group billing systems | Statement: [BT Mobile, billingRelationship, BT Group billing systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billingRelationship Context triple: [BT Mobile, billingRelationship, BT Group billing systems]
-
A.
billing
Indicates that one entity charges another entity for goods or services, typically by issuing an invoice or request for payment.
-
B.
financialRelationshipWith
Indicates a financial connection or association between entities, such as ownership, investment, funding, or other monetary ties.
-
C.
billingAuthorityType
Indicates the specific role or category of authority responsible for issuing or managing a bill in the relationship between the parties.
-
D.
billedBy
chosen
Indicates that one entity issues a bill or invoice to another entity for goods, services, or charges.
-
E.
relationshipTypeWithGoosefatBill
Indicates the specific nature or category of relationship that an entity has with GoosefatBill.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b693a48190a6230b7b52bc8cd3 |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97ee9d881908711dbe12a55283c |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:10 a.m.