Triple
T25274652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telkom |
E633662
|
entity |
| Predicate | formerMonopoly |
P172748
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Telkom, formerMonopoly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerMonopoly Context triple: [Telkom, formerMonopoly, true]
-
A.
monopolyOn
Indicates that one entity has exclusive control or rights over a resource, market, or activity, preventing others from participating on equal terms.
-
B.
monopolySide
Indicates that one party holds exclusive or dominant control in a market or domain relative to the other party.
-
C.
monopolyPrecededBy
Indicates that one monopoly situation or period occurred after and was temporally preceded by another specified event, condition, or monopoly.
-
D.
monopolyFollowedBy
Indicates that one monopoly situation or period is succeeded by another distinct monopoly in time or sequence.
-
E.
monopolyGrantedBy
Indicates that one party has been given exclusive control or rights over a market, resource, or activity by another authority or entity.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 21, 2026, 1:17 p.m.