Triple
T21226076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sy |
E523086
|
entity |
| Predicate | informationExchanged |
P39680
|
FINISHED |
| Object | subscriber charging information |
—
|
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: subscriber charging information | Statement: [Sy, informationExchanged, subscriber charging information]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationExchanged Context triple: [Sy, informationExchanged, subscriber charging information]
-
A.
knowledgeExchange
Indicates a reciprocal sharing or transfer of knowledge, information, or expertise between entities.
-
B.
informationTypeHandled
chosen
Indicates that an entity is responsible for processing, managing, or dealing with a particular type or category of information.
-
C.
sharesInformationWith
Indicates that one entity communicates or provides information to another entity.
-
D.
typeOfInformation
Indicates that one entity specifies the category or kind of information that characterizes or describes another entity.
-
E.
exchanged
Indicates a reciprocal transfer of something (such as information, goods, or services) between two or more entities.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734ab3f6c819083e277ea1c33134e |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:44 p.m.