Triple
T35631822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RS-MMC |
E1029607
|
entity |
| Predicate | wasCommonInEra |
P119523
|
FINISHED |
| Object | early 2000s mobile devices |
—
|
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: early 2000s mobile devices | Statement: [RS-MMC, wasCommonInEra, early 2000s mobile devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCommonInEra Context triple: [RS-MMC, wasCommonInEra, early 2000s mobile devices]
-
A.
isPopularInEra
Indicates that an entity enjoys widespread recognition, approval, or influence during a specific historical or cultural time period.
-
B.
livedInEra
Indicates that an entity existed or was active during a particular historical era or time period.
-
C.
usedDuringEraOf
chosen
Indicates that something was in use or actively employed during the time period or historical era associated with another entity.
-
D.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
E.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.