Triple
T34469987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Mobile |
E884879
|
entity |
| Predicate | SIMCardType |
P110576
|
FINISHED |
| Object | 3-in-1 SIM |
—
|
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: 3-in-1 SIM | Statement: [Public Mobile, SIMCardType, 3-in-1 SIM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SIMCardType Context triple: [Public Mobile, SIMCardType, 3-in-1 SIM]
-
A.
hasSIMType
chosen
Indicates that an entity uses or is associated with a specific type or category of SIM (Subscriber Identity Module).
-
B.
carrierType
Indicates the type or category of carrier involved in the relationship or action (e.g., the kind of entity that carries or transports something).
-
C.
cardType
Indicates the classification or category assigned to a card within a given system or context.
-
D.
subscriberIdentityModule
Indicates that one entity functions as the subscriber identity module (SIM) associated with, used by, or installed in another entity.
-
E.
hasSIMConfiguration
Indicates that an entity is associated with or assigned a specific SIM card configuration or setup.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7199dda688190a79d5e73b285f132 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2:01 a.m.