Triple
T21192390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMS |
E522242
|
entity |
| Predicate | messageSizeLimitSomeNetworks |
P142698
|
FINISHED |
| Object | up to 1 MB or more |
—
|
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: up to 1 MB or more | Statement: [MMS, messageSizeLimitSomeNetworks, up to 1 MB or more]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messageSizeLimitSomeNetworks Context triple: [MMS, messageSizeLimitSomeNetworks, up to 1 MB or more]
-
A.
hasCommunicationLimitation
Indicates that an entity is subject to some restriction, constraint, or reduced capacity in its ability to communicate.
-
B.
fileNameLimit
Indicates a constraint or maximum allowed length or format for a file’s name in a given context.
-
C.
householdAccountSizeLimit
Indicates a restriction on the maximum allowable size or capacity of a household account.
-
D.
sizeRestriction
chosen
Indicates that there is a limitation or constraint on the allowable size or dimensions of something in the relationship.
-
E.
memberOfBodySize
Indicates that one entity is a component or part whose size contributes to or characterizes the overall body size of another entity.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73338dbe881908360dedad65c964b |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.